| 1 |
On Monday 22 January 2007 08:53, Dorin wrote: |
| 2 |
> > This suggests that dbus isn't in world or a dep on anything in world. |
| 3 |
> > Hence it should show up on `emerge --depclean -p`. |
| 4 |
> |
| 5 |
> Actually k3b is in my world file and dbus doesn't show up |
| 6 |
> on 'emerge --depclean -p'. |
| 7 |
> |
| 8 |
> > The actual dependency looks like this: |
| 9 |
> > |
| 10 |
> > # grep -A 2 "hal?" $(portageq portdir)/app-cdr/k3b/k3b-0.12.17.ebuild |
| 11 |
> > hal? ( || ( dev-libs/dbus-qt3-old |
| 12 |
> > ( <sys-apps/dbus-0.90 |
| 13 |
> > >=sys-apps/dbus-0.30 ) ) sys-apps/hal ) |
| 14 |
> > |
| 15 |
> > So k3b doesn't depend on dbus if the hal USE flag is disabled or if |
| 16 |
> > dbus-qt3-old is installed. |
| 17 |
> |
| 18 |
> That would explain it, but I checked and dbus-qt3-old isn't installed and |
| 19 |
> an 'equery u k3b' shows k3b actually has the hal USE flag enabled. |
| 20 |
|
| 21 |
Hmm.. Actually this is the exact reason `emerge -avuDN world` don't try to |
| 22 |
upgrade dbus. When you type `emerge -pv dbus` emerge does not check whether |
| 23 |
any packages in world or in your system requires a lower version or blocks |
| 24 |
dbus. It only checks whether there is an upgrade for dbus and upgrades it if |
| 25 |
there is. |
| 26 |
|
| 27 |
If you do that on your next `emerge -avuDN world` you will probably see |
| 28 |
portage pull in dev-libs/dbus-qt3-old because ( <sys-apps/dbus-0.90 |
| 29 |
>=sys-apps/dbus-0.30 ) is no longer satisfied and dev-libs/dbus-qt3-old is |
| 30 |
listed first and hence preferred. |
| 31 |
|
| 32 |
:) |
| 33 |
|
| 34 |
-- |
| 35 |
Bo Andresen |
Archives