On Mon, Feb 24, 2025 at 08:35:13AM -0800, Felix Lechner wrote: > Hi Murilo, > > On Mon, Feb 24 2025, Murilo wrote: > > > generating guix package definitions from Cargo.lock. > > How else can we avoid packaging errors like this one? [1] > > Kind regards > Felix > > P.S. I'm not a Rust person & behind on the conversation. > > [1] https://issues.guix.gnu.org/76444
Currently we have a manifest in etc/teams/rust/rusty-packages.scm which creates a manifest of all the cargo-build-system packages which aren't prefixed with rust- or have rust as an input. It takes about 4 hours to build on my machine, partly due to the firefox derivatives. I only test the "interesting" packages and only test the intermediate rust-* packages when doing updates. Switching to using only the crates imported by parsing the Cargo.lock should remove the need for me to personally test the manifest (I think it might also be on cuirass), and we could use `guix build -P1 foo` like normal when we update a package, since we now really only care about the "interesting" packages, not the source-only cargo inputs. While we could force the packages to use slightly newer versions of their inputs I wouldn't see it as something we'd need to do regularly unless there's a security advisory. Also switching to using the Cargo.lock to create a list of rust crates needed to build the package should eliminate the possibility of incompatible crates in a build. -- Efraim Flashner <efr...@flashner.co.il> אפרים פלשנר GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351 Confidentiality cannot be guaranteed on emails sent or received unencrypted
signature.asc
Description: PGP signature
