Bug 274848 - textproc/py-CommonMark: rename bin/cmark to bin/cmark-py for conflict avoidance
Summary: textproc/py-CommonMark: rename bin/cmark to bin/cmark-py for conflict avoidance
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Some People
Assignee: Romain Tartière
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-11-01 11:18 UTC by John Hein
Modified: 2023-11-11 04:03 UTC (History)
1 user (show)

See Also:
bugzilla: maintainer-feedback? (romain)


Attachments
[patch] bin/cmark -> bin/cmark-py (1.12 KB, patch)
2023-11-01 11:24 UTC, John Hein
jcfyecrayz: maintainer-approval? (romain)
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description John Hein 2023-11-01 11:18:55 UTC
Nothing in the ports tree that I found depend on bin/cmark from textproc/py-CommonMark.

To avoid conflicts with textproc/cmark (and allow removal of secondary conflict marking like 'DOCS_CONFLICTS_BUILD=cmark' in devel/llvm*), renaming bin/cmark in textproc/py-CommonMark to bin/cmark-py seems like a reasonable option.

There is a (slight?) POLA concern that existing downstream users will be affected by this change.  Adjusting to the change by looking for cmark-py does not seem particularly onerous.  Encouraging the upstream project to do so is perhaps even better.  I will pursue that as well.

On github, commonmark/cmark (for textproc/cmark) and readthedocs/commonmark.py (for textproc/py-CommonMark) both started in 2014 with commonmark/cmark barely "winning" by a month or so. There's no clear "prior art" winner based on that distinction.  But I suspect most py-CommonMark users use it as a python module rather than the command line tool.  In the ports tree py-recommonmark uses py-CommonMark and certainly uses it purely as a python module rather than invoking bin/cmark.
Comment 1 John Hein 2023-11-01 11:24:09 UTC
Created attachment 246048 [details]
[patch] bin/cmark -> bin/cmark-py

Rename bin/cmark to bin/cmark-py.

This can be followed up with removal of CONFLICT markers in textproc/cmark and devel/llvm*.
Comment 2 Romain Tartière freebsd_committer freebsd_triage 2023-11-08 21:00:25 UTC
> I suspect most py-CommonMark users use it as a python module rather than the command line tool

Same


All this look reasonable!
Comment 3 commit-hook freebsd_committer freebsd_triage 2023-11-11 01:56:18 UTC
A commit in branch main references this bug:

URL: https://cgit.FreeBSD.org/ports/commit/?id=2c93a03bbcd528fcdce6e06ef7f2b71017e07050

commit 2c93a03bbcd528fcdce6e06ef7f2b71017e07050
Author:     Romain Tartière <romain@FreeBSD.org>
AuthorDate: 2023-11-11 01:42:15 +0000
Commit:     Romain Tartière <romain@FreeBSD.org>
CommitDate: 2023-11-11 01:54:11 +0000

    textproc/py-CommonMark: Allow installation with textproc/cmark

    Both ports install bin/cmark.  Users of textproc/py-CommonMark are
    supposely more interested in the python module rather than the command
    line tool: nothing in the ports tree seems to use bin/cmark from this
    port.

    Rename the command to cmark-py to fix conflict

    PR:             274848
    Reported by:    jcfyecrayz@liamekaens.com

 textproc/cmark/Makefile                           |  2 --
 textproc/py-CommonMark/Makefile                   |  3 +--
 textproc/py-CommonMark/files/patch-setup.py (new) | 11 +++++++++++
 3 files changed, 12 insertions(+), 4 deletions(-)