Summary: | Support 'exp' keyword in profiles.desc | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Joshua Kinard <kumba> |
Component: | Enhancement/Feature Requests | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | rhill, vapier |
Priority: | High | Keywords: | InVCS |
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 216231 | ||
Attachments: | for extensibility, ignore labels other than "stable" or "dev" |
Description
Joshua Kinard
2008-02-24 18:42:21 UTC
sorry for dropping this kumba :/ wolf also wanted a "deprecated" or "dead" or similar keyword so that we could enumerate all profiles in the profiles file, even the deprecated ones If we want to be backward compatible the we'll have to introduce a now file since old versions of repoman will treat an unsatisfied dependency as fatal if the last column contains anything except "dev". i dont think we care. changing the behavior to have repoman warn verbosely on unknown profiles sounds like a saner upgrade path for the future. Created attachment 144749 [details, diff]
for extensibility, ignore labels other than "stable" or "dev"
If we're not going the backward compatibility route, then we'll have to wait until this patch is in stable portage and all devs will then have to upgrade as soon as we start using new labels.
(In reply to comment #3) > i dont think we care. changing the behavior to have repoman warn verbosely on > unknown profiles sounds like a saner upgrade path for the future. Hmm, if there's an unrecognized profile label I guess repoman should advise the user about the problem and bail out (advising them to upgrade). TODO: implement (In reply to comment #5) > (In reply to comment #3) > > i dont think we care. changing the behavior to have repoman warn verbosely on > > unknown profiles sounds like a saner upgrade path for the future. > > Hmm, if there's an unrecognized profile label I guess repoman should advise the > user about the problem and bail out (advising them to upgrade). TODO: implement Makes sense. I was under the impression devs should be using the latest repoman available, since older versions can do things differently that could break the tree (like, the removal of digests and all) This is fixed in 2.1.5_rc1. |