Bug 470670 – repoman should warn about deprecated EAPIs

• Status: RESOLVED FIXED
• Product: Portage Development

[Description Ulrich Müller 2013-05-19 16:03:31 UTC]

Per council decision in the April 2013 meeting (see URL):
"EAPIs 1 and 2 are discouraged. Repoman should warn about this."

[Comment 1 Zac Medico 2013-05-19 16:15:52 UTC]

We could control this with a setting in metadata/layout.conf that specifies which EAPIs are deprecated, like this:

eapis-deprecated = 1 2

[Comment 2 Zac Medico 2013-05-19 16:18:29 UTC]

@pms-bugs: Any feedback for the layout.conf extension proposed in comment #1?

[Comment 3 Ciaran McCreesh 2013-05-19 16:21:11 UTC]

We should probably standardise layout.conf, since people seem to be using it.

[Comment 4 Ulrich Müller 2013-05-19 18:30:18 UTC]

(In reply to comment #1)
> We could control this with a setting in metadata/layout.conf that specifies
> which EAPIs are deprecated, like this:
> 
> eapis-deprecated = 1 2

Repository dependent, so that overlays can have a more (or less?) proactive policy? Good idea.

[Comment 5 Ulrich Müller 2013-05-19 18:35:35 UTC]

Thinking about it, maybe you should foresee both warnings and fatal errors for certain EAPIs.

[Comment 6 Zac Medico 2013-05-20 15:36:20 UTC]

(In reply to comment #5)
> Thinking about it, maybe you should foresee both warnings and fatal errors
> for certain EAPIs.

Maybe something like this then:

eapis-deprecated = 1 2
eapis-banned = 6 7 8

Do we want to support some kind of matching like regular expressions or fnmatch, or is an explicit list of EAPIs good enough?

[Comment 7 Ciaran McCreesh 2013-05-20 15:42:05 UTC]

A list is fine.

[Comment 8 Zac Medico 2013-05-24 04:49:19 UTC]

This is fixed in git:

http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commit;h=7f164c6fd1c47c254b1e1df101edb680492c0c12

[Comment 9 Zac Medico 2013-05-24 05:50:09 UTC]

This is fixed in 2.1.12.2 and 2.2.0_alpha177.

I've added "eapis-deprecated = 1 2" to metadata/layout.conf in CVS.