Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 5075 - settings-change awareness
Summary: settings-change awareness
Status: RESOLVED FIXED
Alias: None
Product: Portage Development
Classification: Unclassified
Component: Core - Interface (emerge) (show other bugs)
Hardware: x86 Linux
: High enhancement (vote)
Assignee: Portage team
URL:
Whiteboard:
Keywords: InVCS
: 33766 (view as bug list)
Depends on:
Blocks:
 
Reported: 2002-07-16 03:01 UTC by cwillisf
Modified: 2004-10-22 08:48 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
Python script to perform the suggested enhancement (useupdate,2.67 KB, text/plain)
2002-07-17 16:09 UTC, cwillisf
Details

Note You need to log in before you can comment on or make changes to this bug.
Description cwillisf 2002-07-16 03:01:04 UTC
Hopefully this hasn't already been listed, but here goes...
I think it would be cool to have an option to emerge to make it run through the
currently-installed packages checking if changes in the USE flags would affect
that package, and if so re-emerge it. That way if you installed vim, then added
"gnome" to your USE flags, emerge would rebuild the vim package so that you now
had gvim. I know "emerge -e world" will do this but isn't that kind of like
swatting a fly with a bus? ;)
This could also be extended to notice changes to CFLAGS / CXXFLAGS, but that
doesn't seem very useful to me since it seems that would end up doing 99% of an
"emerge -e world" anyway... so if that were done it would probably need to be a
separate flag from the one to notice USE changes...
Comment 1 cwillisf 2002-07-17 16:09:35 UTC
Created attachment 2344 [details]
Python script to perform the suggested enhancement
Comment 2 Marius Mauch (RETIRED) gentoo-dev 2003-12-13 17:41:15 UTC
*** Bug 33766 has been marked as a duplicate of this bug. ***
Comment 3 Marius Mauch (RETIRED) gentoo-dev 2004-10-06 11:23:02 UTC
--newuse in 2.0.51
Comment 4 Nicholas Jones (RETIRED) gentoo-dev 2004-10-22 08:48:13 UTC
Bug has been fixed and released in stable portages on or before 2.0.51-r2