SEO

Sometimes when doing the following emerge, some new packages wants to be
emerged, why is this exactly?
And how to check why each package wants to be added?


4_2400 ~ # emerge --pretend --verbose --update --newuse --deep --color=n
world

These are the packages that would be merged, in order:

Calculating world dependencies... done!
[ebuild N ] dev-libs/libevent-1.3a 0 kB
[ebuild N ] net-libs/libnfsidmap-0.17 USE="-ldap" 0 kB
[ebuild U ] net-fs/nfs-utils-1.0.10 [1.0.6-r6]
USE="tcpd -kerberos% -nonfsv4%" 0 kB
[ebuild U ] www-client/mozilla-firefox-2.0.0.2 [2.0.0.1-r4]
USE="java -debug -filepicker -gnome -ipv6 -mozbranding -mozdevelop -moznopango -restrict-javascript -xforms -xinerama -xprint"
LINGUAS="da
de -af% -ar -be% -bg -ca -cs -el -en_GB -es -es_AR -es_ES -eu -fi -fr -fy -fy_NL -ga -ga_IE -gu -gu_IN -he -hu -it -ja -ka -ko -ku -lt -mk -mn -nb -nb_NO -nl -nn -nn_NO -pa -pa_IN -pl -pt -pt_BR -pt_PT -ru -sk -sl -sv -sv_SE -tr -zh -zh_CN -zh_TW"
0 kB
[ebuild U ] net-misc/openssh-4.5_p1-r1 [4.5_p1] USE="X pam
tcpd -X509 -chroot -hpn -kerberos -ldap -libedit
(-selinux) -skey -smartcard -static" 0 kB
[ebuild U ] sys-apps/dbus-1.0.2-r1 [1.0.2] USE="X doc -debug (-selinux)"
0 kB

Total: 6 packages (4 upgrades, 2 new), Size of downloads: 0 kB

lars <lars@hesdorf.dk> wrote:
> Sometimes when doing the following emerge, some new packages wants to
> be
> emerged, why is this exactly?
> And how to check why each package wants to be added?
>
>
> 4_2400 ~ # emerge --pretend --verbose --update --newuse --deep
> --color=n
> world
>
> These are the packages that would be merged, in order:
>
> Calculating world dependencies... done!
> [ebuild N ] dev-libs/libevent-1.3a 0 kB
> [ebuild N ] net-libs/libnfsidmap-0.17 USE="-ldap" 0 kB
> [ebuild U ] net-fs/nfs-utils-1.0.10 [1.0.6-r6]
> USE="tcpd -kerberos% -nonfsv4%" 0 kB

In this case, libnfsidmap is needed by nfs4, which is new to nfs-utils
version 1.0.10, and will thus be pulled in automatically (unless you specify
the nonfsv4 USE flag). Likewise, libevent is also needed either by the new
version of nfs-utils or libnfsidmap. You can tell by the emerge order --
the dependencies are pulled in first, and then the packages that require
them.

If you have gentoolkit installed, you can use "equery depends
newpackagename" to find out what uses it, and "equery depgraph packagename"
to list all dependencies for a package.

Regards,
--
*Art

On Sat, 24 Feb 2007 10:13:02 +0100, lars wrote:

> Sometimes when doing the following emerge, some new packages wants to be
> emerged, why is this exactly?
> And how to check why each package wants to be added?
>
>
> 4_2400 ~ # emerge --pretend --verbose --update --newuse --deep --color=n
> world

# emerge -vpuNDt world

Arthur Hagen wrote:

> lars <lars@hesdorf.dk> wrote:
>> Sometimes when doing the following emerge, some new packages wants to
>> be
>> emerged, why is this exactly?
>> And how to check why each package wants to be added?
>>
>>
>> 4_2400 ~ # emerge --pretend --verbose --update --newuse --deep
>> --color=n
>> world
>>
>> These are the packages that would be merged, in order:
>>
>> Calculating world dependencies... done!
>> [ebuild N ] dev-libs/libevent-1.3a 0 kB
>> [ebuild N ] net-libs/libnfsidmap-0.17 USE="-ldap" 0 kB
>> [ebuild U ] net-fs/nfs-utils-1.0.10 [1.0.6-r6]
>> USE="tcpd -kerberos% -nonfsv4%" 0 kB
>
> In this case, libnfsidmap is needed by nfs4, which is new to nfs-utils
> version 1.0.10, and will thus be pulled in automatically (unless you
> specify
> the nonfsv4 USE flag). Likewise, libevent is also needed either by the
> new
> version of nfs-utils or libnfsidmap. You can tell by the emerge order --
> the dependencies are pulled in first, and then the packages that require
> them.
>
> If you have gentoolkit installed, you can use "equery depends
> newpackagename" to find out what uses it, and "equery depgraph
> packagename" to list all dependencies for a package.
>
> Regards,

Thanks, but how to see that the USE flag nonfsv4 is involved in the first
place?