acrichto: I'm interested in making sure cargo works well with nix
bjz_ joined the channel
bjz has quit
bennofs has quit
rgrinberg has quit
Andoriyu has quit
Andoriyu joined the channel
starblue has quit
starblue joined the channel
JanC_ joined the channel
JanC has quit
Andoriyu has quit
bjz_ has quit
kimundi- joined the channel
Lateralus joined the channel
kimundi has quit
kimundi- is now known as
Lateralus has quit
Noldorin has quit
brson joined the channel
brson has quit
Cardoe
acrichto: I took a peek at your cargo-vendor and its similar-ish to how I've packaged up Rust (and really Cargo built) applications in both Gentoo and Yocto. I'm effectively creating a custom CARGO_HOME but one that mirrors the official look of the repo. I'm fetching a snapshot of the crates.io-index and fetching down the actual crate dependencies using the official package manager of each distro.
Was wondering if you thought I should instead make a custom index. I was using the official one since I eventually want to let all the packages share the same CARGO_HOME
and I noticed that cargo-vendor starts up by letting cargo::execute_main_without_stdin() but when I looked at cargo-fmt it just used a normal main() and parsed options itself. Is there a preferred way to create cargo extensions?
I'm writing cargo-bitbake and cargo-ebuild which take a crate (binary crate, not library) and create a package for Yocto and Gentoo respectively.
sfackler
Cardoe: I use execute_main_without_stdin for my subcommand
Cardoe
ok good to know
I'll switch over to that
p32blo joined the channel
p32blo has quit
p32blo1 joined the channel
p32blo joined the channel
p32blo1 has quit
acrichto
Cardoe: yeah in the long run I wouldn't actually create a custom index (it's brittle and we'll have more official solutions soon)
but for now it should work
p32blo has quit
p32blo joined the channel
p32blo1 joined the channel
p32blo has quit
Cardoe
ok good deal.
p32blo1 has quit
p32blo joined the channel
basically both distros are source based but due to how they work I can't actually let cargo fetch anything. Everything has to be defined in a recipe / ebuild file.
p32blo has quit
p32blo joined the channel
p32blo has quit
p32blo1 joined the channel
and they both compile in a sandboxed environment that has no network so I've got to get things ready for cargo before cargo is even called.
p32blo joined the channel
p32blo1 has quit
p32blo has quit
I suspect rpms and debs will likely use something similar too. But I could be wrong.