Hi,
On Fri, 02 Jul 2021 at 10:52, zimoun wrote:
> On mar., 27 déc. 2016 at 16:10, ng0 wrote:
>
>> ng0@wasp ~$ guix import crate net2
>> following redirection to
>> `https://crates-io.s3-us-west-1.amazonaws.com/crates/net2/net2-0.2.26.crate'...
>> (package
>> (name "rust-net2")
>> (version "
Hi,
On mar., 27 déc. 2016 at 16:10, ng0 wrote:
> ng0@wasp ~$ guix import crate net2
> following redirection to
> `https://crates-io.s3-us-west-1.amazonaws.com/crates/net2/net2-0.2.26.crate'...
> (package
> (name "rust-net2")
> (version "0.2.26")
> (source
> (origin
> (method url
> Could the importer be changed to either ignore targets that don’t match
> the current architecture or to uniquify the list of inputs?
It could, but I don't see an advantage. It takes more than just
removing duplicate inputs for the thing to build. I'd find time spent
on a Cargo.lock parser (whic
David Craven 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 = "
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.depen
I'm on the grand journey into rusty land, and while I'm
assembling a list of what needs to be packaged to package our
prototype, I got this:
ng0@wasp ~$ guix import crate net2
following redirection to
`https://crates-io.s3-us-west-1.amazonaws.com/crates/net2/net2-0.2.26.crate'...
(package
(name
