| Summary: | emerge -e world lists glibc as new, but man emerge says it shouldn't | ||
|---|---|---|---|
| Product: | Portage Development | Reporter: | David Morgan <david.morgan> |
| Component: | Core | Assignee: | Portage team <dev-portage> |
| Status: | RESOLVED INVALID | ||
| Severity: | normal | ||
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
-e pretends nothing is installed So will the man page be changed? to what ? the manpage looks fine to me The man page says that the list of installed packages is tweaked to only include glibc, which isn't what seems to be happening, and isn't what SpanKY said happens I know I'm not the only person to be confused by this |
from man emerge: --emptytree (-e) Virtually tweaks the tree of installed packages to only contain glibc; this is great to use together with --pretend. This allows developers to get a complete overview of the complete dependency tree of a package, and it enables complete trees to be rebuilt using the latest libraries. But, emerge -ep[uD] world | grep glibc (or emerge -ep[uD] portage | grep glibc) Gives this: [ebuild N ] sys-libs/glibc-2.3.4.20040619 Adding the -t option, shows (skipping the [ebuild N]s: sys-libs/libstdc++-v3-3.3.3-r1 sys-apps/sed-4.0.9 sys-lib/glibc-2.3.4.20040619 emerge -s glibc lists this version as the latest installed and the latest available, btw If glibc is supposed to be left in the list of installed packages, surely it should be being emerged by these commands, and it almost certainly shouldn't be listed as being new Reproducible: Always Steps to Reproduce: