Control: severity -1 important Hi,
Quoting Arnaud Ferraris (2024-08-02 22:24:09) > It's not strictly "breaking" anything, but I'm packaging tuba[1] which > is now built against libclapper, and I'd appreciate if this package could: > * build-depend only on libclapper-dev (or whatever) rather than the > whole clapper package > * depend only on libclapper rather than all of clapper > * not have to explicitly build-depend on libclapper-dev's dependencies; > this is somehow orthogonal to the split, but without the split those > should be made dependencies of clapper itself, which is clearly > suboptimal (no need for a mere video player to pull a whole bunch of > gstreamer development files) > > This would bring a (admittedly minor) improvement to bandwidth usage for > buildds and disk usage for users, not mentioning the fact that it aligns > with current practice in Debian. you do not need to convince me with more than "tuba needs it". ;) For the most of its existance, libclapper was only an internal implementation which was not supposed to be used by others. This changed with the recent (2 weeks ago) upload of clapper 0.6. Since then, libclapper is supposed to be used by others with the caveat that its API is still not deemed to be stable. Thus, I did not yet split up the packaging into clapper and libclapper-dev with my upload 2 weeks ago and was waiting if somebody even would need it because if that's not the case, why bother FTP master and increase the package count in the archive? Now that tuba needs it, the split has to be done. If you want it be done faster, feel free to submit a patch either via the BTS or as a MR against the clapper packaging repository. Thanks! cheers, josch
signature.asc
Description: signature
