Re: [bug#51845] [CORE-UPDATES] librsvg and rust

On Wed, Dec 08, 2021 at 02:36:11PM +, Ricardo Wurmus wrote: > > Ludovic Courtès writes: > > > Hello! > > > > For the record, this is a followup to Efraim’s proposal in > > . > > > > Efraim Flashner skribis: > > > >> Option 1: > >> Track down the ~220 crate

Re: [CORE-UPDATES] librsvg and rust

On Wednesday, December 8th, 2021 at 6:36 AM, Ricardo Wurmus wrote: > Ludovic Courtès l...@gnu.org writes: > > > Hello! > > > > For the record, this is a followup to Efraim’s proposal in > > > > https://issues.guix.gnu.org/51845. > > > > Efraim Flashner efr...@flashner.co.il skribis: > > > > > Op

Re: [CORE-UPDATES] librsvg and rust

Ludovic Courtès writes: > Hello! > > For the record, this is a followup to Efraim’s proposal in > . > > Efraim Flashner skribis: > >> Option 1: >> Track down the ~220 crates which form the dependency graph (of crates) >> for librsvg and pin them until the nex

Re: [CORE-UPDATES] librsvg and rust

Hello! For the record, this is a followup to Efraim’s proposal in . Efraim Flashner skribis: > Option 1: > Track down the ~220 crates which form the dependency graph (of crates) > for librsvg and pin them until the next core-updates cycle. Continue > like with

[CORE-UPDATES] librsvg and rust

Core-updates is almost done which means we need to come to a decision about librsvg and the rust crates. The problem: The librsvg tarball includes bundled rust crates. We normally unbundle bundled sources, and we just so happen to have a) replacement crates for the bundled ones, b) a method to rep