File conflict between cmark and python3-commonmark

[travankor]

System

• xuname:
  Void 5.10.73_1 x86_64 GenuineIntel uptodate hold rrrmDDFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
• package:
  cmark-0.30.2_1 and python3-commonmark-0.9.1_2

Expected behavior

No file conflicts

Actual behavior

File conflicts

xbps-query -Rf cmark
/usr/bin/cmark
...
xbps-query -Rf python3-commonmark
/usr/bin/cmark
...

Steps to reproduce the behavior

xbps-query -Rf cmark
xbps-query -Rf python3-commonmark

[ericonr]

Thoughts on preference? Are the command line flags similar?

I can see a case for alternatives or just renaming the script from the python package.

[ericonr]

(assuming python3-commonmark is depended on by other packages, having it conflict would be far from ideal)

[bobertlo]

arch just renamed the python3-commonmark binary to /usr/bin/py3-cmark fwiw. I really think between the two noone is installing python3-commonmark to use that cmark cli.

If the commands were separate from the libraries I doubt this conflict would come up often, but with both packages providing libraries it's not a great situation.

[ericonr]

I think we usually spell out "python3-" in these executable names, but if other distros use py3 it might help to go with the flow. I will check them out.

[bobertlo]

Yeah, that was just an example I was also thinking python3 might be more appropriate.

I noticed alpine and fedora both appear to have this conflict. I really don't think anyone will have an issue about the filename, but I could see someone installing both of these packages.

[github-actions]

Issues become stale 90 days after last activity and are closed 14 days after that. If this issue is still relevant bump it or assign it.