Peter Alfredsen <[email protected]> wrote: > I think we should start > deprecating EAPI=0 usage *now* with a repoman warning whenever a new > ebuild is committed that does not use EAPI=1 or EAPI=2. This warning > should encourage use of the newest EAPI, EAPI=2.
A general question, that just popped into my head when i was reading this: if i touch a ebuild which has EAPI=0, should i bump it to EAPI=2? Since the introduction of EAPI i have been bumping EAPI of my ebuilds based on need. So if i needed slot-deps, i've made the ebuild EAPI=1, not EAPI=2 by choice. If i needed use-deps, then well, i went for EAPI=2. How are other ebuild developers doing this? What's the package manager ppls take on this? -- Regards, Matti Bickel Signed/Encrypted email preferred (key 4849EC6C)
pgpr5TMoF3mbY.pgp
Description: PGP signature
