Gentoo Archives: gentoo-dev

From: Alec Warner <antarus@g.o>
To: gentoo-dev@l.g.o
Subject: [gentoo-dev] Stable Staleness (mostly toolchain)
Date: Sun, 30 Jul 2006 17:09:07
Message-Id: 44CCAE94.5000306@gentoo.org
As the lead for the treecleaner project (team, whatever you want to call
it wolf ;) ), I've been trying to fix old broken packages, many have
been slated for removal, some have had minor fixes, and others are still
setting waiting for me to get some free time.

Another class of packages I wish to discuss (not remove quite yet, just
talking ;) ) are older packages with stable markings.  By Stable I mean
debian stable, IE we stabled it in 2004 and no one has touched it since.

Do these packages still work with a current system (linux 2.4/2.6,
glibc-2.3/2.4, >=gcc-3.4, etc...

So partially this is a question for gcc porting, how many *known broken*
apps don't get fixed when we upgrade and stable a gcc version.  Do these
stay in the tree, and do they have deps on older versions of gcc
(effectively masking them, since old versions of gcc generally get
masked by profile eventually).

How many apps are just sitting in the tree and no one knows if they
compile at all with a recent system?

Solar already has some decent tinderboxing scripts, it would be
interesting to me to have a system to keep track of the known state of
certain categories of packages that are...less used ;)

I think also that genone's Gentoo-Stats project would be a great
information aggregator as we could identify packages that no one uses
anymore.

Anyway, these were just some thoughts I had about trimming the tree a
bit; feel free to rip em apart as always :0

-Antarus
-- 
gentoo-dev@g.o mailing list

Replies

Subject Author
Re: [gentoo-dev] Stable Staleness (mostly toolchain) Denis Dupeyron <calchan@g.o>
[gentoo-dev] Re: Stable Staleness (mostly toolchain) Ryan Hill <dirtyepic.sk@×××××.com>