Hi Devs, I'm wondering whether it wouldn't make sense to require eclasses (or strongly encourage) to include an explicit list of EAPIs it has been tested for in order to ease testing when introducing new EAPIs.
We have seen some issues already with EAPI6 bump related to get_libdir and people updating EAPI in ebuild without properly testing the inherited eclasses. having a whitelist in place and die if eclass is not updated to handle it solves it. Thoughts? comments? cookies? threats? -- Kristian Fiskerstrand OpenPGP certificate reachable at hkp://pool.sks-keyservers.net fpr:94CB AFDD 3034 5109 5618 35AA 0B7F 8B60 E3ED FAE3
signature.asc
Description: OpenPGP digital signature
