> 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
1. Boot from an installation-os image.
2. cp /etc/issue /tmp
3. ls -l /tmp[observe that /tmp/issue exists]
4. mount -t ext4 /dev/sda1 /mnt
5. herd start cow-store /mnt
6. ls -l /tmp [observe that /tmp/issue has dissappeared]
J'
--
Avoid eavesdropping. Send strong encrypted email.
PGP Publi
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 = "
