Hi,
On 7/13/25 22:03, Ilya Orlov wrote:
Upstream gamescope[1] have several embedded copies which current
packaging changes for system libraries (except reshade patch[2]).
I have the same problem with ngscopeclient -- it has several copies of
imgui and stb, because there are inconsistent versions along the
dependency tree.
It also has one dependency that is meant to be configured by providing a configuration header on the include search path, and while my personal preference is that this code be lit on fire, I believe there are users
who want this software.
Preliminary packages live in
https://deb.simonrichter.eu/sjr-misc-sid.sources
in case anyone is interested.
Right now I have the package split so the various dependencies come as
separate source packages, and the various libraries unified. The plan
would be to rename all the source packages and add an "ngscopeclient"
suffix to show that these are meant mostly as build dependencies and
should not be used for anything else (which would be kind of a case
against shipping them in Debian proper -- these binary packages would
only ever be installed on autobuilders, so burdening the mirror network
and everyone's package lists with them is not really great).
I'm not sure that is sustainable if the various upstreams go out of sync
again. If I were to fold everything back into a single source package
with lots of orig archives, is there a procedure to make the security
team aware of the embedded copies?
Would it make sense to add a field to the Source stanza listing variants
of other source packages that are embedded?
Simon
--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)