Bug 566398

Summary:	layout.conf: Allow EAPIs via allowed-eapis= whitelist rather than banning them
Product:	Portage Development	Reporter:	Michał Górny <mgorny>
Component:	Enhancement/Feature Requests	Assignee:	Portage team <dev-portage>
Status:	CONFIRMED ---
Severity:	normal	CC:	qa
Priority:	Normal
Version:	unspecified
Hardware:	All
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---

Description Michał Górny archtester

2015-11-21 17:03:04 UTC

Right now we deprecate and ban old EAPIs in layout.conf. However, we have no way of making repoman refuse non-standard EAPIs or new EAPIs.

I'd say we introduce a new variable stating which EAPIs are allowed, i.e.:

  allowed-eapis = 0 1 2 3 4 5 6

which would effectively ban EAPIs 7 as well as 5-progress, etc.

(CC-ing qa@ for opinion)

Comment 1 Zac Medico gentoo-dev

2015-11-21 18:27:08 UTC

Maybe it makes sense to support boolean attribute, or EAPI categories of some sort, so that we don't have to explicitly list all of the "official gentoo" EAPIs.

Boolean example:

   official-gentoo-eapis-only = true
   official-gentoo-eapi-max = 6

Category example:

  allowed-eapi-categories = official-gentoo
  official-gentoo-eapi-max = 6

The official-gentoo-eapi-max attribute is only needed if we want to prevent new official EAPIs from being automatically allowed.