-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 30/08/12 08:37 AM, Michael Mol wrote: > On Thu, Aug 30, 2012 at 7:29 AM, Johannes Huber <[email protected]> > wrote: > > [snip] > >>> Developers have only a limited amount of time, and this will >>> eat into it. The result is likely to not be new shiny ebuilds >>> that use the new EAPIs, but rather old rusty ones that still >>> use the old EAPI but also which contain other bugs, since they >>> don't get touched at all (since touching them triggers the new >>> policy). >> >> You dont need to touch the old ebuild, but if you are touching it >> for example a version bump, a bug fix etc you should be able to >> do the EAPI bump as long as you have done the ebuild quizzes ;) > > I'm a proxy maintainer. Meaning I haven't done these quizzes. > Heck, I've never even seen them. I catch bug reports, come up with > a solution and pass it back to Markos, who then decides whether or > not to put it in and give feedback. > > How would this impact me? >
If you are rewriting a full ebuild as your solution, and the ebuild you start with is EAPI<4 , then Markos would appreciate it if you changed the ebuild to be EAPI=4 (or whatever the latest EAPI is) in addition to the fix. Otherwise, just do what you do and Markos "should" bump the ebuild to EAPI=4 when he applies your fixes. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iF4EAREIAAYFAlA/Y1gACgkQ2ugaI38ACPCq1wEAowuUqEMzAj1vFXFrE0fkOkEi gt4rKXXuCCxgb0h11WABAKsMa/7OI2dqX/JA6eXSYOAfsdm5vI7IUCY4MirLlT6s =jwzi -----END PGP SIGNATURE-----
