Le 17/08/2011 21:57, Matthew Summers a écrit : > +1 on this. It saves the ebuild for posterity AND prevents users > hitting nasty bits. This seems to me to beg for a proper well-defined > policy, in any case. >
We already have a policy for this and it's called portage. If a package is broken (and I mean with known ebuild issues, with known bugs, etc), then we already have legitimate reasons to remove it. If not, just let them be in portage. If anything, working on tinderboxes to catch build issues early and file bugs against packages, _that_ would help to clean up cruft from portage. Rémi
