-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 30/08/12 09:04 AM, Rich Freeman wrote: > On Thu, Aug 30, 2012 at 8:58 AM, Ian Stakenvicius <a...@gentoo.org> > wrote: >> 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. > > And if he doesn't have time to do that, he'll just go ahead and > ignore your bug and users can make do without the fix. :) > > Rich >
I think you may miss the meaning of "should". It's not the same as "must". IE, when bug or security fixes happen, i'm pretty sure it's still OK to apply those (even when bumping the ebuild) as soon as possible even though the ebuild isn't EAPI=4. The idea here is to not let old EAPI's sit around in the tree forever, not to halt all maintenance. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iF4EAREIAAYFAlA/ZX8ACgkQ2ugaI38ACPCUWQD/azjLKkv6Mpa1tLuupSuOM5AZ O1y83kdzWAYqeU/4tZAA/i/+8kEhOf76UDxm3f8K1AhOxQp7GUg/mO2MBRStdln+ =hM58 -----END PGP SIGNATURE-----
