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.
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*.
> I suspect most py-CommonMark users use it as a python module rather than the command line tool Same All this look reasonable!
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(-)
A commit in branch main references this bug: URL: https://cgit.FreeBSD.org/ports/commit/?id=78c7700b5c2bd7501137472e754fb640b486ee1a commit 78c7700b5c2bd7501137472e754fb640b486ee1a Author: Brooks Davis <brooks@FreeBSD.org> AuthorDate: 2024-10-01 23:11:09 +0000 Commit: Brooks Davis <brooks@FreeBSD.org> CommitDate: 2024-10-01 23:16:46 +0000 devel/llvm19: 19.1.1 release Remove obsolete build conflict with cmark. PR: 239636, 274848 devel/llvm19/Makefile | 3 +-- devel/llvm19/distinfo | 6 +++--- 2 files changed, 4 insertions(+), 5 deletions(-)
A commit in branch main references this bug: URL: https://cgit.FreeBSD.org/ports/commit/?id=7cea690fddbd4f6bb3ad3360e625754bde7ac4e6 commit 7cea690fddbd4f6bb3ad3360e625754bde7ac4e6 Author: Brooks Davis <brooks@FreeBSD.org> AuthorDate: 2024-10-01 23:15:29 +0000 Commit: Brooks Davis <brooks@FreeBSD.org> CommitDate: 2024-10-01 23:16:46 +0000 devel.llvm[12345678]: remove cmark conflict [NFC] The build conflict with cmark is no longer needed. PR: 239636, 274848 devel/llvm11/Makefile | 1 - devel/llvm12/Makefile | 1 - devel/llvm13/Makefile | 1 - devel/llvm14/Makefile | 1 - devel/llvm15/Makefile | 1 - devel/llvm16/Makefile | 1 - devel/llvm17/Makefile | 1 - devel/llvm18/Makefile | 1 - 8 files changed, 8 deletions(-)