On Fri, 11 Dec 2009 08:59:14 -0800 Brian Harring wrote: > One potential compromise- tag in a section in pms about "nonstandard > eapis" and throw in some links to places folks can look. That > general approach should provide a way to retire standardized EAPIs > from the doc also- same thing "go look here". Why bother? That's quite a bit of work. Instead, what's wrong with a gradual, carefully controlled phasing out? The first step (preventing people from installing any more kdebuild-1 things) was already done recently, when the genkdesvn repo was removed. The second step (ensuring that people no longer have kdebuild-1 packages installed) can be done with the next major Paludis release. The third step (removing it from everywhere) can be left until after we've given everyone reasonable time to clean up. Doing things that way has little to no cost and little to no user impact, whereas rushing to remove kdebuild-1 without thought for the effects reeks of "huh huh, let's try to wind people up". -- Ciaran McCreesh