i may not understand this well enough, but with that in mind...
the nix crowd allows something that they call vendoring: they use the native
tools of the language ecosystem to fetch the transitive closure of the
dependencies, as specified by their own package management descriptions. then
they
Am Fri, Aug 25, 2023 at 03:56:56PM +0100 schrieb (:
> Zhu Zihao writes:
> > and AFIAK, Maxime Devos is working on new build system called
> > "Antioxidant", which can build rust application without cargo (Yes,
> > invoke rustc directly!), The new build system will cache the rlib
> > intermediate r
Zhu Zihao writes:
> and AFIAK, Maxime Devos is working on new build system called
> "Antioxidant", which can build rust application without cargo (Yes,
> invoke rustc directly!), The new build system will cache the rlib
> intermediate result of crate and share between different builds.
Sadly, I
Jonas Møller writes:
> Hi Guix! Why does cargo-build-system need #:cargo-inputs specified in the
> package definition? This seems like a big
> mistake for a couple of reasons.
Just like the nice people in mail list explained, when building a
package, Guix builders are not allowed to connect to
Hi,
Sorry if I came off a bit harsh in the initial reply :) I didn't intend
for it to read as a "ugh, how don't you understand this" sort of thing
but that's what it appeared to be looking at it later.
(Communication: It's Hard™)
Aaanyway
Jonas Møller writes:
> Interesting, Guix alrea
Interesting, Guix already has git/url-fetch, what is keeping Guix from simply
fetching a cargo project and then running `cargo build` in the fetched source
directory?
If the problem is that the build daemon is sandboxed and doesn't have internet
access, it is also feasible to have one stage of
Jonas Møller writes:
> Hi Guix! Why does cargo-build-system need #:cargo-inputs specified in the
> package definition? This seems like a
> big mistake for a couple of reasons.
>
> 1 It is completely redundant, it should match what is in Cargo.toml. I know
> `guix import crate` exists to
> autom
Hi Guix! Why does cargo-build-system need #:cargo-inputs specified in the
package definition? This seems like a big mistake for a couple of reasons.
- It is completely redundant, it should match what is in Cargo.toml. I know
`guix import crate` exists to automate this process, but I don't unders
