On Mon, 2004-02-02 at 13:27, Brian Jackson wrote: > One problem I have with this is that it says all ebuilds should remain in the > tree for a minimum of one year. 4 releases a year, and every package in the > tree is going to have 4 versions that can't be cleaned out for at least a > year. Not to mention that it's going to be hard to get developers in to the > mindset of saving old ebuilds when we've been beating them ruthlessly about > keeping portage clean for the past 6 months at least. Do you have any ideas > about how to deal with this?
I see no point in keeping "stable" ebuilds in the regular tree once they've been moved over to the stable tree. At that point they could be pruned. Donnie
signature.asc
Description: This is a digitally signed message part
