| Summary: | --newuse flags are not displayed for removed flags unless --verbose is enabled | ||
|---|---|---|---|
| Product: | Portage Development | Reporter: | Carsten Lohrke (RETIRED) <carlo> |
| Component: | Core | Assignee: | Portage team <dev-portage> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | Keywords: | InVCS |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Bug Depends on: | |||
| Bug Blocks: | 181949 | ||
| Attachments: | show --newuse flags that trigger reinstallation even when not in --verbose mode | ||
|
Description
Carsten Lohrke (RETIRED)
2007-07-27 18:44:47 UTC
(In reply to comment #0) > You can ignore most of the crap, but please notice the pointless rebuilds, e.g. > zlib or ghostscript. Apparently those were flag removals ("build" for zlib and "emacs" for ghostscript-esp). I'll fix it so those get displayed. > Beside this you see also the test use flag induced rebuilds. Form my POV it > would be better, if the test use flag would supercede the feature flag, when > set in /etc/portage/package.use. Different bug or do you all strongly disagree? > So, you want the flag in package.use to enable the test phase even when FEATURES=test is disabled, and you want -flag in package.use to disable FEATURES=test even though it is enabled? Maybe we can do something like that. Unfortunately, circular interactions like this often lead to strange logic that is annoying to maintain. FWIW, you can already use /etc/portage/profile/package.use.mask to explicitly disable tests on certain packages. Created attachment 126192 [details, diff]
show --newuse flags that trigger reinstallation even when not in --verbose mode
This is fixed in svn r7408.
This has been released in 2.1.3. > So, you want the flag in package.use to enable the test phase even when > FEATURES=test is disabled, and you want -flag in package.use to disable > FEATURES=test even though it is enabled? Maybe we can do something like that. > Unfortunately, circular interactions like this often lead to strange logic that > is annoying to maintain. Yes, I can follow you here. It's just irritating to have a feature that sort of breaks distinct functionality. > FWIW, you can already use /etc/portage/profile/package.use.mask to explicitly > disable tests on certain packages. Didn't thought about that. Will work for me. Right now the relationship between FEATURES=test and USE=test is one-way-only, the feature adds (but doesn't remove if disabled) the use flag, so if you mask the use flag the test phase would still run (but probably fail if the additional dependencies are missing). And I'd rather not hack another special case into portage to make it bi-directional, the real solution you're after would be package.features. |