Kristian Fiskerstrand <k...@gentoo.org> writes: > inherited eclasses. having a whitelist in place and die if eclass is not > updated to handle it solves it. > > Thoughts? comments? cookies? threats?
Wouldn't a blacklist be more practical than a whitelist? root# cat /usr/portage/profiles/eclass.eapi.mask fooutils.eclass >=6 The problem seems infrequent enough that a blacklist is sufficient, like all the *.mask files in /usr/portage/profiles. The whitelist places a large testing burden on eclass authors on each EAPI bump, where 99% of the time there won't be any issue to fix. Erik
