From: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] Packages can't depend on package-$version
Date: Tue, 17 May 2022 04:14:21 +0200 [thread overview]
Message-ID: <20220517021421.MkxZLOIXO7-rSwIexzDJOrR8zrHYDorwEcd3a_8kLxY@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-28665@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1018 bytes --]
Closed issue by ericonr on void-packages repository
https://github.com/void-linux/void-packages/issues/28665
Description:
See 0961351b5226020b44bc8f1426310112c9151055
`util-linux` shouldn't have to be revbumped every time `util-linux-libs` is, or vice versa. Changes that only affect one of the packages should allow us to revbump only one of them, but that currently isn't possible, because `util-linux` has `util-linux-libs-${version}_${revision}` in `depends`. The ABI is unlikely to change between revisions (we even depend on it not changing between versions). Therefore, it should be possible to depend on `util-linux-libs-${version}`, which currently results in the package not being found: `=> ERROR: util-linux-2.36.1_2: target dependency 'util-linux-libs-2.36.1' does not exist!`.
It would be nice to define a mechanism for depending on a specific *version* of a package, without caring about specific revision. I believe other templates could also be improved if such a mechanism becomes available.
prev parent reply other threads:[~2022-05-17 2:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-11 14:05 [ISSUE] " ericonr
2021-02-11 17:28 ` Chocimier
2022-05-03 2:14 ` github-actions
2022-05-17 2:14 ` github-actions [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220517021421.MkxZLOIXO7-rSwIexzDJOrR8zrHYDorwEcd3a_8kLxY@z \
--to=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).