On Mon, Feb 02, 2004 at 12:27:08PM -0600 or thereabouts, 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?
Valid point. One suggestion I would have would be to add a "date created" stamp to each ebuild (or perhaps this information is already there in the header somewhere). Then, we can track that info across the whole stable tree so the developer wouldn't have to worry about it. That is to say that, once it makes it into the stable tree, the developer isn't responsible for ensuring it stays there for a year -- it's up to the maintainers of the stable tree (gentoo-server unless releng wants the job). I also like this solution because it would allow us to do useful things like publish a schedule of when various ebuilds will be retired so users can check them ahead of time and plan accordingly. --kurt
pgp00000.pgp
Description: PGP signature
