-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 08/20/2013 01:01 PM, Michał Górny wrote: > Hello, > > Due to the widespread breakage in the tree noted in bug #480892 > [1], and mis-design of multilib-minimal.eclass, we'd like to put > some more work into getting einstalldocs() ready for EAPI 6.
Ok, I'm too lazy to wait for a reply, so here you go Let's check what misdesign is: * creating eclasses with too many phases and those wrapped a thousand times, so no one really knows how it works anymore and ebuild writers are confused and often miss things; other devs have already complained about that obscurity * creating python eclasses that rely so heavily on useflags that it causes a lot of pain for users because of blockers (just read #gentoo) and adding/removing python version and then adding another bunch of python_single_foo* which cause even more useless rebuilds for users * creating a distutils eclass that fails for some packages, because it doesn't let you control how setup.py is called properly * updating vcs-snapshot eclass to drop support for an archive type, because the author is unable to make his code improvement work with it * creating multilib eclasses that are widely untested and dumping all the slow migration pain including multilib-specific bugs, countless blockers users have to deal with and all the emul-linux-x86-* updating stuff on everyone not really misdesign, but rather misbehavior: * refusing to slow down when told that your solutions may cause problems for other developers * refusing to work with other devs who demand an alternative implementation * trying to force other people to use a solution that they feel is not fit, because they want minimum reliance on eclasses which autotools-utils is NOT (and for the record, you do not follow PMS standard there) * requesting features for other peoples eclasses and then blaming them for misdesign, although YOU have even REVIEWED the changes If you keep on with this behavior, then I hope you know where that leads. I don't mind strong discussions and most points in the first chapter will not make me say "it was the wrong choice" (everyone knows that I am all pro migrating), but you are becoming someone people do not want to work with. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.20 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJSFKhuAAoJEFpvPKfnPDWzNX4H/AlQ+neoEUfnE4MCuyQKVifZ 1iMva9NjoO3xCQcSjyYmq0tOBeKbRbErdy0G2vca4JkX1fZnDiEQe+NCzMRIJBKl rTHYiDAaVg/ZTP+f1E0FXoPgS1t6NCjF/hKelniUGoYcxSKMJ5nA+z0/JuKQfzGF bsEkT44XXpliZAFOjuxSFMBl7NdCkt9XMBrX5tIdQj38XaVtnelvJII6TJ+hUsnj 8MVyui3d030X96Ezxe2k2kiqZRbqYCYQkU44zPeh/3Ns0O7mJ0/c0EidW1PcCvcZ ZS31GsPJV7zsl3HVlHuNmJDf3+WcNc8p06fRfG7iCS3nLGmsAEZBOc1y0oWvIVo= =PfTn -----END PGP SIGNATURE-----
