[Midnightbsd-cvs] [MidnightBSD/mports] 7ca860: textproc/cmark, textproc/py-CommonMark: let both i...

[Lucas Holt]

  Branch: refs/heads/master
  Home:   https://github.com/MidnightBSD/mports
  Commit: 7ca860c7844f1c97e8ddca6a98399ee8eeadfc30
      https://github.com/MidnightBSD/mports/commit/7ca860c7844f1c97e8ddca6a98399ee8eeadfc30
  Author: Lucas Holt <luke at foolishgames.com>
  Date:   2026-09-06 (Sun, 06 Sep 2026)

  Changed paths:
    M textproc/cmark/Makefile
    M textproc/py-CommonMark/Makefile
    A textproc/py-CommonMark/files/patch-setup.py

  Log Message:
  -----------
  textproc/cmark, textproc/py-CommonMark: let both install together (#846)

`textproc/cmark` and `textproc/py-CommonMark` both installed `bin/cmark`
and each listed the other in `CONFLICTS_INSTALL`, so only one could ever
be installed.

That is not theoretical: `mail/evolution` needs `libcmark.so` from
`textproc/cmark`, and on a system with `py-CommonMark` installed it
cannot be rebuilt —

```
mport.install: install failed: Error at check_preconditions.c:(595):
  /usr/local/bin/cmark is owned by py312-CommonMark; use -f to overwrite.
```

### Fix

Follow FreeBSD's resolution (commit `2c93a03bbcd5`): patch the python
port's `setup.py` to name its console script `cmark-py`, then drop
`CONFLICTS_INSTALL` from both ports. Users of `py-CommonMark` want the
Python module; nothing in the tree calls its `bin/cmark`.

Both ports get a `PORTREVISION` bump since their packing lists change.

### Why one PR for two ports

The change is a single coupled edit — dropping `CONFLICTS_INSTALL` from
`textproc/cmark` alone would permit a genuine file conflict until the
python port is patched, so the two halves must land together. FreeBSD
committed it as one change for the same reason. Happy to split if you'd
rather.

### Testing (amd64, MidnightBSD 4.1)

- `py-CommonMark` rebuilt and reinstalled: now ships `bin/cmark-py` →
`cmark-py-3.12`, and `bin/cmark` is free
- `textproc/cmark` then built and installed alongside it with no
conflict
- `mail/evolution`, which had been failing,
rebuilt/staged/packaged/reinstalled cleanly
- Both `cmark-0.30.3_2` and `py312-CommonMark-0.9.1_2` are now installed
simultaneously

🤖 Generated with [Claude Code](https://claude.com/claude-code)

https://claude.ai/code/session_01RfjmwisLNPFuZeaQCUJn4A

## Summary by Sourcery

Enable cmark and py-CommonMark to coexist by giving the Python package a
distinct command name and removing their installation conflicts.

Bug Fixes:
- Allow the cmark and py-CommonMark ports to be installed simultaneously
without file conflicts.

Enhancements:
- Rename the Python package's console command from cmark to cmark-py and
remove the mutual installation conflicts.

Chores:
- Bump both ports' PORTREVISION values to reflect their packaging
changes.

Signed-off-by: Lucas Holt <luke at foolishgames.com>
Co-authored-by: Claude Opus 5 (1M context) <noreply at anthropic.com>



To unsubscribe from these emails, change your notification settings at https://github.com/MidnightBSD/mports/settings/notifications