From: Efraim Flashner <efraim@flashner.co.il>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Cc: 45058@debbugs.gnu.org
Subject: bug#45058: Duplicate inputs with Crate importer
Date: Wed, 9 Dec 2020 10:38:13 +0200 [thread overview]
Message-ID: <X9CM9fbv1iusfHiT@E5400> (raw)
In-Reply-To: <87ft4knexa.fsf@nicolasgoaziou.fr>
[-- Attachment #1: Type: text/plain, Size: 1304 bytes --]
On Sat, Dec 05, 2020 at 10:03:45PM +0100, Nicolas Goaziou wrote:
> Hello,
>
> I noticed the Crate importer sometimes returns duplicate inputs. For
> example
>
> guix import crate bat
>
> returns
>
> ...
> (arguments
> `(#:cargo-inputs
> (("rust-ansi-colours" ,rust-ansi-colours-1)
> ("rust-ansi-term" ,rust-ansi-term-0.12)
> ("rust-atty" ,rust-atty-0.2)
> ("rust-clap" ,rust-clap-2)
> ("rust-clap" ,rust-clap-2)
> ...
As noted here¹ rust-clap-2 is listed as both a dependency and a
build-dependency. For the sake of completeness, there are also packages
which require the same crate+version for cargo-dev-input and a looser
version requirement for cargo-input. It seems worthwhile to deduplicate
the cargo-inputs, since it's a combination of 'dependencies' and 'build
dependencies', but I'm not sure about removing duplicates when they
appear in both cargo-inputs and cargo-development-inputs.
¹ https://crates.io/crates/bat
>
> Regards,
> --
> Nicolas Goaziou
>
>
>
--
Efraim Flashner <efraim@flashner.co.il> אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2020-12-09 8:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-05 21:03 bug#45058: Duplicate inputs with Crate importer Nicolas Goaziou
2020-12-09 8:38 ` Efraim Flashner [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=X9CM9fbv1iusfHiT@E5400 \
--to=efraim@flashner.co.il \
--cc=45058@debbugs.gnu.org \
--cc=mail@nicolasgoaziou.fr \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.