On 29/03/2021 11:32, Fabio Valentini wrote:
There are two examples of how to work around this issue: - The ruby package bundles a bunch of gems in addition to the Ruby interpreter, and while some of the gem subpackages have different versions, there's only *one* Release tag in the whole package, and it never gets reset to 0 so the upgrade path for all subpackages works out fine. - The rust package ships the rust compiler and some tools (cargo, rustfmt, rls), and they have different "upstream" versions, but since they are never exposed to the user, these are ignored in Fedora, and just inherit the main version of the package, i.e. the version of the Rust compiler itself.
There's also what nodejs does where the npm subpackage has the npm version but the nodejs version and release combined are used as the release for the subpackage, for example: nodejs-14.16.0-1.fc33.x86_64 npm-6.14.11-1.14.16.0.1.fc33.x86_64 That ensures that npm has the "correct" version but also that it will also be upgraded when nodejs upgrades. Tom -- Tom Hughes (t...@compton.nu) http://compton.nu/ _______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
