| 1 |
On Tue, Jul 03, 2007 at 03:39:11AM +0300, Daniel Iliev wrote: |
| 2 |
> On Mon, 2 Jul 2007 14:06:25 -1000 |
| 3 |
> Joshua Hoblitt <jhoblitt@××××××××××.edu> wrote: |
| 4 |
> |
| 5 |
> > Is there a CLI utility to add/remove values from 'world' without |
| 6 |
> > causing packages to be emerged/unemerged? Even the emerge --inject |
| 7 |
> > functionality is gone. Or for that mater, is there even a way of |
| 8 |
> > listing what's in world? I've gotten into the habit of editing |
| 9 |
> > /var/lib/portage/world by hand but I always feel 'dirty' for doing |
| 10 |
> > this. |
| 11 |
> > |
| 12 |
> > -J |
| 13 |
> > |
| 14 |
> > -- |
| 15 |
> |
| 16 |
> |
| 17 |
> From "man emerge" |
| 18 |
> |
| 19 |
> --noreplace (-n) |
| 20 |
> Skips the packages specified on the command-line |
| 21 |
> that have already been installed. Without this option, any |
| 22 |
> packages, ebuilds, or deps you specify on the command-line |
| 23 |
> will cause Portage to remerge the package, even if it is already |
| 24 |
> installed. Note that Portage will not remerge dependencies by |
| 25 |
> default. |
| 26 |
> |
| 27 |
> This adds packages to "world". I manually edit the file when I want to |
| 28 |
> remove some packages from "world" w/o actually uninstalling them. |
| 29 |
|
| 30 |
Yes, I agree that -n will causes packages to be added to world but it |
| 31 |
also causes them to be emerged immediately which is not always desired. |
| 32 |
A practically example of this usage case is where your about to run an |
| 33 |
`emerge -DNuva world` or `emerge -e world` and you want to make |
| 34 |
modifications to 'world'. |
| 35 |
|
| 36 |
-J |
| 37 |
|
| 38 |
-- |
Archives