From: Andrew Gaffney <agaffney@skylineaero.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] odd dependencies
Date: Sat, 15 May 2004 12:00:33 -0500 [thread overview]
Message-ID: <40A64CB1.4090401@skylineaero.com> (raw)
In-Reply-To: <200405160150.08158.jstubbs@gentoo.org>
Jason Stubbs wrote:
> On Sunday 16 May 2004 00:43, Andrew Gaffney wrote:
>
>>>Marius Mauch wrote:
>>>
>>>>On 05/14/04 Andrew Gaffney wrote:
>>>>
>>>>>In my digging for how Portage really works, I've come across yet
>>>>>another oddity. In 'emerge -ep xfree', I get:
>>>>>
>>>>>[ebuild N ] sys-devel/bc-1.06-r5
>>>>>
>>>>>but 'qpkg -q -nc -I bc' shows:
>>>>>
>>>>>sys-libs/glibc-2.3.3_pre20040420
>>>>>DEPENDED ON BY:
>>>>> elfutils-0.94-r1
>>>>> prelink-20040317
>>>>>sys-devel/bc-1.06-r5 <---------
>>>>>DEPENDED ON BY: <---------
>>>>> SYSTEM PROFILE <---------
>>>>>dev-libs/libcroco-0.5.1
>>>>>DEPENDED ON BY:
>>>>> librsvg-2.6.4
>>>>>dev-libs/libcdio-0.66
>>>>>DEPENDED ON BY:
>>>>> vcdimager-0.7.20
>>>>>
>>>>>If bc is only in the system profile and not depended on by anything
>>>>>else, why is it getting dragged in by xfree?
>>>>
>>>>Because portage checks the system profile everytime, not just for
>>>>`emerge system`.
>>>
>>>Then why doesn't the *entire* system profile get included?
>
>
> Something wrong with qpkg it seems... it probably doesn't check further if
> it's a system package.
>
> bc < openssl < perl < xfree
Wasn't there supposed to be a Python/Perl rewrite of qpkg?
--
Andrew Gaffney
Network Administrator
Skyline Aeronautics, LLC.
636-357-1548
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2004-05-15 17:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-15 4:53 [gentoo-dev] odd dependencies Andrew Gaffney
2004-05-15 13:34 ` Marius Mauch
2004-05-15 15:43 ` Andrew Gaffney
2004-05-15 16:50 ` Jason Stubbs
2004-05-15 17:00 ` Andrew Gaffney [this message]
2004-05-16 1:32 ` [gentoo-dev] python/perl rewrite of qpkg Andrew Ross
2004-05-17 9:24 ` [gentoo-dev] odd dependencies Karl Trygve Kalleberg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=40A64CB1.4090401@skylineaero.com \
--to=agaffney@skylineaero.com \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox