Sometimes (quite a few times) I have several packages installed that I have
modified and do not want to upgrade them with a newer package (or even after
specificing -U, emerge still wants to downgrade the package).
It would be really nice to have an --exclude option to /usr/bin/emerge so that
these packages will not be written over.
I'm busy and don't want to spend all day upgrading becuase mozilla takes a long
time to compile:
# /usr/bin/emerge -UD world --exclude mozilla
I have customized a package with encryption options and wish to upgrade the
# /usr/bin/emerge -UD world --exclude util-linux
Some options to "--exclude" could be:
- specified individual packages names
- a file containing a list of package names
Currently, I'm doing "emerge -UDp world > ~/emerge.list" (removing the misc
markings within that file to only include package names) and then running the
# Small script to compile emerge a list of source names
# contained within a file called /home/roger/tmp/emerge.list
while read file; do
emerge -U $file
} < /root/emerge.list
either pin the files in your world file or mask versions you dont want upgraded in
This is a duplicate of Bug 16342
However, the original post neglects to mention my scenario.
The resolution posted for Bug 16342 also does not solve my solution and is merely a workaround.
I think many basic binaries include sometime of "--exclude" option. (ie. fgrep)
On a side note, this would probably be called a "feature of a feature". Allot of us install "masked" packages and a "emerge -UDp world" may fail becuase a masked package is installed and conflicts. Maybe "--exclude" could also be incorporated to ignore the package. ...or maybe this "feature of this feature" should be called "--ignore".. well, getting OT here.
i think my comment #1 and Bug 16342 address everything mentioned here
*** This bug has been marked as a duplicate of 16342 ***
*** Bug 31563 has been marked as a duplicate of this bug. ***
yup. ditto. i would prefer a command line option "--exclude" also.