From: "Ludovic Courtès" <ludo@gnu.org>
To: Tobias Geerinckx-Rice <me@tobias.gr>
Cc: guix-devel@gnu.org
Subject: Re: How should ambiguous package specifications be handled?
Date: Sat, 25 Jan 2020 18:35:44 +0100 [thread overview]
Message-ID: <8736c3a173.fsf@gnu.org> (raw)
In-Reply-To: <87r1zqmskn.fsf@nckx> (Tobias Geerinckx-Rice's message of "Thu, 23 Jan 2020 10:26:48 +0100")
Hello,
Tobias Geerinckx-Rice <me@tobias.gr> skribis:
> Christopher Baines 写道：
[...]
>> Given there do seem to be ways of avoiding these ambiguous package
>> specifications, would it be helpful to have a lint warning that
>> identifies a package as being ambiguous (as it shares the name and
>> version with another package)?
>
> That's a good idea at the very least. I don't think such duplication
> is ever justified.
I agree, a ‘lint’ warning would be nice.
However, I think that tools like Cuirass and the Data Service must be
able to cope with duplicates; they should not consider name+version as a
unique key for packages.
Ludo’.
next prev parent reply other threads:[~2020-01-25 17:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-23 8:03 How should ambiguous package specifications be handled? Christopher Baines
2020-01-23 9:26 ` Tobias Geerinckx-Rice
2020-01-25 17:35 ` Ludovic Courtès [this message]
2020-01-26 10:16 ` Christopher Baines
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8736c3a173.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=me@tobias.gr \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).