On Tue, 2024-09-24 at 20:32 +0100, Simon McVittie wrote: > On Wed, 21 Aug 2024 at 23:45:30 +0200, Guillem Jover wrote: > > On Sat, 2024-04-27 at 17:40:49 +0800, Maytham Alsudany wrote: > > > +A package statically linked with the libraries contained in the > > > +librust-gtk4-dev and librust-pulsectl-rs-dev binary packages, where > > > +the latter is licensed under GPL-3+ (a license that requires full > > > +source code to be available), would have these fields in its control > > > +file: > > > + > > > +:: > > > + > > > + Built-Using: rust-pulsectl-rs (= 0.3.2-1+b1) > > > + Static-Built-Using: rust-gtk4 (= 0.7.3-3), rust-pulsectl-rs (= > > > 0.3.2-1+b1) > > With this interpretation of the relationship between the two fields, > is there any situation where a source package would validly appear in > Built-Using but not in Static-Built-Using? (Other than the obvious > "this package has not yet been updated to implement Static-Built-Using")
I don't believe so (at least not in any scenario I can think of). Thanks, -- Maytham Alsudany Debian Maintainer maytham @ OFTC maytha8 @ Libera
signature.asc
Description: This is a digitally signed message part