-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 12/10/12 04:38 PM, Walter Dnes wrote: > On Fri, Oct 12, 2012 at 12:53:15PM +0200, Ralph Sennhauser wrote >> From time to time the topic of deprecating EAPIs comes up and >> usually one suggestion is to keep 0 and start with converting >> EAPI 1 ebuilds. Then someone comes along and asks what is the >> point? Indeed, a fair question. > > It's my understanding that higher EAPI levels include more > features. How backwards compatable are the EAPI levels? I.e. > assume that we take an ebuild with EAPI 0, and slap in EAPI=1 (or 2 > or 3, etc) at the top, without any other changes. Are there any > circumstances where the ebuild would behave differently and/or > break?
Yes. There is more than just new features that have been added. Some default operations have changed. Eclass behaviour can also be different. I'll let others go into the details, but one of the big changes between EAPIs is the way an unspecified DEPEND or RDEPEND is handled. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iF4EAREIAAYFAlB4gVYACgkQ2ugaI38ACPB45QD+PC6PvspnXdmOhMAEOIDPxh2m 4RDWrTw8t86O+iyKodsA/RdRo1r1Xxc734hXbAwtZlxjC3KcU/mnGQVysvflOdjW =uk9m -----END PGP SIGNATURE-----
