On 24 March 2014 12:18, Lennart Poettering <mzerq...@0pointer.de> wrote:
> > > It's a pity though that nobody in Fedora is actively working on getting > rid of legacy cruft. I really wished we had some people who oversee > deprecating things more proactively, figure out how to deprecate things, > write stub code to provide smooth transitions, write release notes and > so on. Being at the bleeding edge of things also means deciding that > some things really should go, from time to time... Besides deprecating > old cruft like libwrap, this would also mean removing all the old crap > from comps "standard" that we still install by default (894110)... > > Old cruft is in the OS because for some set of people it is useful, and it is very hard to design around stuff people think should be there because it was there before. The only way to get around that is to build something completely new with a different 'brand' which does not have expectations from people already there. I think you would have a better chance starting from a ground zero and putting new wine in a new winesack versus trying to put it in an old one and then wondering why it keeps bursting. -- Stephen J Smoogen.
-- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
