Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 54248 - emerge needs options to disclude an ebuild from -u runs manually
Summary: emerge needs options to disclude an ebuild from -u runs manually
Status: RESOLVED DUPLICATE of bug 16342
Alias: None
Product: Portage Development
Classification: Unclassified
Component: Enhancement/Feature Requests (show other bugs)
Hardware: All Linux
: High enhancement (vote)
Assignee: Portage team
Depends on:
Reported: 2004-06-17 20:20 UTC by Eitan Mosenkis
Modified: 2005-07-17 13:06 UTC (History)
0 users

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


Note You need to log in before you can comment on or make changes to this bug.
Description Eitan Mosenkis 2004-06-17 20:20:57 UTC
When you run emerge in ways that will install multiple ebuilds, you need to be able to specifically tell it not to install certain packages (or upgrade, downgrade, remove, or otherwise touch them)
For instance:
I had problems with X and eventually solved some of them by installing 4.3.99.  It used to be that using -uU would stop it from replacing 4.3.99 with 4.3.0, but now it seems to have dissapeared from the portage tree, so -uU doesn't work anymore.  Thus, if I could run emerge with something like: emerge -uU --not xfree then I could continue to update my packages automatically without it destroying X, which is the worst thing I can think of to have to keep changing. (Config files are screwy)

Reproducible: Always
Steps to Reproduce:
1.Install xfree 4.3.99 somehow
2.Run emerge -pUu world
3.See that it still wants to downgrade xfree and theres no way to stop it except not using -u and doing it one by one

Actual Results:  
It tries to emerge xfree 4.3.0 despite the downgrade

Expected Results:  
It should have a way to stop it from changing xfree at all until theres an upgrade
Comment 1 SpanKY gentoo-dev 2004-06-17 20:28:40 UTC
4.3.99 has disappeared because you're supposed to be using xorg-x11 :P

`emerge -i x11-base/xfree-4.3.0-r7`

*** This bug has been marked as a duplicate of 16342 ***