| 1 |
On Fri, 08 Jun 2012 21:28:19 +0200 |
| 2 |
Jarry <mr.jarry@×××××.com> wrote: |
| 3 |
|
| 4 |
> On 08-Jun-12 18:38, Nikos Chantziaras wrote: |
| 5 |
> >> I just noticed there is new stable portage-utils ebuild |
| 6 |
> >> (for amd64) but my system does not want to update it |
| 7 |
> > |
| 8 |
> > Is it in your world file? If not, either add it, or add |
| 9 |
> > "--with-bdeps=y" in the emerge command. |
| 10 |
> |
| 11 |
> This solves the issue, but it is strange: portage-utils are |
| 12 |
> not in my world file, so why are they installed? I suppose |
| 13 |
> this ebuild was maybe included in "system" at the time of |
| 14 |
> installation and later removed. But if it is so, why is |
| 15 |
> this "orphaned package" not uninstalled whenever I run |
| 16 |
> "emerge --depclean"? |
| 17 |
|
| 18 |
It's not orphaned, and AFAIK portage-utils was never in @system. |
| 19 |
|
| 20 |
But pambase DEPENDs on portage-utils, do you have pambase installed? |
| 21 |
|
| 22 |
Portage's default behaviour is to ignore build-time deps for emerges |
| 23 |
and consider them for --depclean. This makes sense and avoids |
| 24 |
unnecessary compiles if an update is only required to build something |
| 25 |
else, not merely to run it. You appear to have hit this exact thing. |
| 26 |
|
| 27 |
"equery depends portage-utils" will tell you the depends, then you can |
| 28 |
look in each of those ebuilds to see what kind of dependancy it is. |
| 29 |
|
| 30 |
|
| 31 |
-- |
| 32 |
Alan McKinnnon |
| 33 |
alan.mckinnon@×××××.com |
Archives