From: Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de>
To: David Craven <david@craven.ch>
Cc: 25281@debbugs.gnu.org
Subject: bug#25281: rust importer duplicates input
Date: Wed, 28 Dec 2016 13:06:28 +0100 [thread overview]
Message-ID: <idjeg0sgsvv.fsf@bimsb-sys02.mdc-berlin.net> (raw)
In-Reply-To: <CAL1_immr3jcxCDJxjYUpO5o8sxVsorW-t7178Vzd55kCGrG3-w@mail.gmail.com>
David Craven <david@craven.ch> writes:
> Looking at the Cargo.toml file we see this:
>
> [target."cfg(unix)".dependencies]
> libc = "0.2.14"
> # Compat with older Cargo versions temporarily
> [target.x86_64-unknown-linux-gnu.dependencies]
> libc = "0.2.14"
> [target.i686-unknown-linux-gnu.dependencies]
> libc = "0.2.14"
> [target.x86_64-apple-darwin.dependencies]
> libc = "0.2.14"
> [target.i686-apple-darwin.dependencies]
> libc = "0.2.14"
>
> I started reimplementing cargos dependency resolution algorithm, but
> think now that it's better to use a Cargo.lock file when one is
> provided.
>
> When there isn't a cargo lock file it's a library in the sense that it
> is a collection of source code that can be reused in a cargo project
> that has a Cargo.lock file.
>
> I don't think that this is a issue that needs fixing.
Could the importer be changed to either ignore targets that don’t match
the current architecture or to uniquify the list of inputs?
~~ Ricardo
next prev parent reply other threads:[~2016-12-28 12:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-27 16:10 bug#25281: rust importer duplicates input ng0
2016-12-28 0:01 ` David Craven
2016-12-28 12:06 ` Ricardo Wurmus [this message]
2016-12-28 20:51 ` David Craven
2021-07-02 8:52 ` zimoun
2021-07-03 7:54 ` zimoun
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=idjeg0sgsvv.fsf@bimsb-sys02.mdc-berlin.net \
--to=ricardo.wurmus@mdc-berlin.de \
--cc=25281@debbugs.gnu.org \
--cc=david@craven.ch \
/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).