| 1 |
On 火, 2002-10-01 at 22:00, Nicolas Kaiser wrote: |
| 2 |
> I'm having difficulties understanding why "emerge -ep" deprives me of |
| 3 |
> useful information about packages that are already installed, or in |
| 4 |
> different version. |
| 5 |
> |
| 6 |
> Is there a special reason for --emptytree testing in this place? |
| 7 |
> |
| 8 |
> TIA, |
| 9 |
> Nicolas |
| 10 |
|
| 11 |
You are asking emerge to pretend and "emptytree" install of a given |
| 12 |
package, from emerge --help |
| 13 |
|
| 14 |
--emptytree (-e short option) |
| 15 |
Virtually tweaks the tree of installed packages to only contain |
| 16 |
glibc, this is great to use together with --pretend. This makes |
| 17 |
it possible for developers to get a complete overview of the |
| 18 |
complete dependency tree of a certain package. |
| 19 |
|
| 20 |
You are being "deprived" of information about installed packages, |
| 21 |
because as far as emerge is concerned you have no installed packages |
| 22 |
(except glibc) when you run emerge with the -e / --emptytree switch |
| 23 |
|
| 24 |
Stuart |
Archives