formula: mity/md4c - #502
MeteorsLiu wants to merge 2 commits into
Conversation
![fennoai[bot]](https://avatars.githubusercontent.com/in/1924301?s=60&v=4){kind=small}
There was a problem hiding this comment.
The formula build paths and consumer checks are sound across the three pinned releases. The generated pkg-config metadata has one compatibility regression: it publishes the Git tag spelling as the package version, so standard numeric version constraints no longer recognize the installed library.
| parserPC := pkgconfig.new( | ||
| name = "MD4C", | ||
| description = "Markdown parser library with a SAX-like callback-based interface.", | ||
| version = version, |
There was a problem hiding this comment.
[P1] Publish the numeric release in pkg-config metadata
Using release-0.5.3 as the pkg-config Version makes normal consumers fail numeric constraints: for example, pkg-config --exists 'md4c >= 0.4.8' returns false even though this is the 0.5.3 release. The upstream .pc template publishes 0.5.3, and the same tag-derived value is emitted by the 0.4.8 and 0.5.0 formulas. Use the numeric version (for example, strings.trimPrefix(fromVer, "release-")) for Version and the HTML renderer's Requires constraint in all three release formulas, while retaining the tag spelling only for fromVer/source selection.
1 participant
Adds the pinned Conan Center md4c recipe as an idiomatic LLAR Formula with source-proven thresholds, options, relocatable pkg-config metadata, and a consumer test.
Closes #255