On Sunday 21 January 2007 23:08, Dorin Scutarasu wrote: > I just noticed that when I do 'emerge -avuDN world' not all packages get > > updated to the last stable version: > > $ emerge -pvuDN world [SNIP] > > Total: 0 packages, Size of downloads: 0 kB > > ...but than... > > > $ emerge -pv dbus [SNIP] > > [ebuild U ] sys-apps/dbus-1.0.2 [0.62-r2] USE="X -debug -doc [SNIP] > ... so I can update to sys-apps/dbus-1.0.2. Also, I see that there are
This suggests that dbus isn't in world or a dep on anything in world. Hence it
should show up on `emerge --depclean -p`.
> packages that need <sys-apps/dbus-0.90:
> > $ equery d dbus
> > [ Searching for packages depending on dbus... ]
> > app-cdr/k3b-0.12.17 (hal? <sys-apps/dbus-0.90)
> > (hal ? >=sys-apps/dbus-0.30)
> > (hal ? >=sys-apps/dbus-0.30)
> > [...]
>
> ... so shouldn't portage prevent me from updating to dbus-1.0.2 since there
> are ebuilds that depend on <sys-apps/dbus-0.90?
The actual dependency looks like this:
# grep -A 2 "hal?" $(portageq portdir)/app-cdr/k3b/k3b-0.12.17.ebuild
hal? ( || ( dev-libs/dbus-qt3-old
( <sys-apps/dbus-0.90 >=sys-apps/dbus-0.30 ) )
sys-apps/hal )
So k3b doesn't depend on dbus if the hal USE flag is disabled or if
dbus-qt3-old is installed.
--
Bo Andresen
pgpufy7Kb0zJE.pgp
Description: PGP signature
