On 10/01/26 11:51, Antoine Le Gonidec wrote:
Le Sat, Jan 10, 2026 at 09:15:01AM +0100, Sébastien Noel a écrit :
Can't we keep GTK2 in the archive like src:gcc-3.3 was ?
With no active development, just making sure it still builds.
I would love to keep the ability to install GTK2 libraries (both amd64 and i386)
from Debian repositories. Many non-free Unity3D video games rely on a plugin
named ScreenSelector.so to provide the user with display option (including
setting the main screen and the game window size), this plugin is linked
against GTK2.
One of Debian's familiar refrains is "this package can be removed,
nothing in (Debinan|the archive) uses it". I think it is a valuable
stance, and I used this reasoning in a couple of RM tickets.
But I now wonder if it makes sense to move to a sort of ports-like
approach for notable libraries (GTK2, old Qt versions) used by external
applications and non-free software. Just as a pragmatic courtesy toward
Debian's users.
My idea in a few bullet points (drawing on what others have stated in
this thread):
* A legacy library can remain in the main archive if...
* USED: There must be proof of the widespread use of this library inside
and outside Debian.
* TEAM MAINTAINED: The library package must be maintained by a team.
* EXPLICITLY OWNED: All team members must be listed as Uploaders.
* MARKED AS LEGACY: d/README.source explicitly describes the legacy
status of this package.
* SECURE: Known security issues must be fixed in unstable and stable in
X days, or the FTP masters will permanently remove the library. (This
may imply that the team is now the new upstream.)
* NO BURDEN: No modifications to the builders nor specific outdated
versions of compilers/runtime environments are required to build the
binary packages.
Regards,
--
Gioele Barabucci
