| Summary: | repoman should warn about deprecated EAPIs | ||
|---|---|---|---|
| Product: | Portage Development | Reporter: | Ulrich Müller <ulm> |
| Component: | Repoman | Assignee: | Portage team <dev-portage> |
| Status: | RESOLVED FIXED | ||
| Severity: | enhancement | CC: | council, pms |
| Priority: | Normal | Keywords: | InVCS |
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| URL: | http://www.gentoo.org/proj/en/council/meeting-logs/20130409-summary.txt | ||
| See Also: | https://bugs.gentoo.org/show_bug.cgi?id=543316 | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Bug Depends on: | |||
| Bug Blocks: | 468524 | ||
|
Description
Ulrich Müller
2013-05-19 16:03:31 UTC
We could control this with a setting in metadata/layout.conf that specifies which EAPIs are deprecated, like this: eapis-deprecated = 1 2 @pms-bugs: Any feedback for the layout.conf extension proposed in comment #1? We should probably standardise layout.conf, since people seem to be using it. (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. Thinking about it, maybe you should foresee both warnings and fatal errors for certain EAPIs. (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? A list is fine. This is fixed in git: http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commit;h=7f164c6fd1c47c254b1e1df101edb680492c0c12 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. |