Hello Efraim,
Thanks for investigating this - a Rust development workflow using only
Guix-native crates is something I've been waiting for!
I was experimenting with your patches and it seems that they do pull in the
source crates for requested packages, but not their dependencies (example
below).
On Wed, Mar 6, 2024 at 4:06 AM Efraim Flashner
wrote:
> On Mon, Feb 26, 2024 at 09:24:29PM -0500, Jason Conroy wrote:
> > Hello Efraim,
> >
> > Thanks for investigating this - a Rust development workflow using only
> > Guix-native crates is something I've
On Thu, Mar 7, 2024 at 3:08 AM Efraim Flashner
wrote:
> The transitive dependencies getting pulled in automatically should work
> automatically if we ever finish the antioxidant-build-system.
Since you bring up antioxidant, I'm kind of curious whether that stalled
mainly due to shifts in contri
On Tue, Mar 12, 2024 at 11:12 AM Efraim Flashner
wrote:
> On Thu, Mar 07, 2024 at 11:48:53AM -0500, Jason Conroy wrote:
> > On Thu, Mar 7, 2024 at 3:08 AM Efraim Flashner
> > wrote:
> >
> > > Until then
> > > I've been experimenting by manually list
Efraim Flashner writes:
Currently if you were to pull in rust-rand-0.8 and rust-rand-0.7
then
you'd have both rand-0.*.crate files in the registry but only
one of
them would be listed in share/cargo/registry/index/ra/nd/rand. I
need to
adjust the generation of that file to combine multiple
Efraim Flashner writes:
On the other hand, by generating it during the build of each
package we
make sure to pull in all the crates which exist in the build, so
we
could add into a profile/manifest just the crates listed in a
Cargo.toml
and then each crate would pull in its own dependencies,
Efraim Flashner writes:
[[PGP Signed Part:Undecided]]
On Wed, Apr 24, 2024 at 11:58:22AM -0400, Jason Conroy wrote:
Efraim Flashner writes:
> On the other hand, by generating it during the build of each
> package we
> make sure to pull in all the crates which exist in the build,
