On 15.08.23 19:19, Simon McVittie wrote:
On Tue, 15 Aug 2023 at 18:41:49 +0200, Matthias Geiger wrote:the latest rsvg would need ~ 10 NEW rust packages if it were to be devendored. iirc you can actually run "cargo vendor" and it would revendor the tarball (even with out upstream vendoring it).Given the policy that Jeremy linked to, I imagine Ubuntu will want to produce a fully-vendored tarball, even if Debian does not.
looks like it, yeah.
We vendor rustc and cargo (partially / before build ) so I wouldn't say the team objects in this case.Producing a fully-vendored tarball of 2.55 or higher would be the closest thing to the status quo, so I think that would be a valid way to update librsvg, even if the Debian Rust team would prefer us to do it differently.
I think so, yeah. The debian cargo wrapper (script) ( |/usr/share/cargo/bin| )||allows linking from a) the system and b) any other directory (or both)Is it possible to vendor *some* dependencies, and take others from Debian? That seems a lot more feasible to me than de-vendoring literally everything, and in particular would avoid librsvg getting stuck behind a new Rust library getting through NEW.
The wrapper mentioned has the documentation inside, you can also checkout my WIP packaging here [0]. All I'd add here for a second vendor dir
would be a |$(CARGO) prepare-debian debian/cargo_registry vendor-dir |( I think). cargo will sort it out then.
werdahias[0] https://salsa.debian.org/werdahias/obfuscate-wip/-/blob/debian/master/debian/rules
||
OpenPGP_0x18BD106B3B6C5475.asc
Description: OpenPGP public key
OpenPGP_signature
Description: OpenPGP digital signature
