| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
On Thursday 19 December 2002 17:04, Riyad Kalla wrote: |
| 5 |
> Pieter, |
| 6 |
> Did you emerge QT 3.1.1 then reemerge the KDE libs? I don't know if this |
| 7 |
> is "overkill" but is it possible that would have fixed the situation? |
| 8 |
> |
| 9 |
> I've seen quite a few people mention the surprise of emerging a new QT |
| 10 |
> lib, then having KDE break... I sort of assume this to happen since you |
| 11 |
> are changing the underlying lib, but maybe I am the one that is |
| 12 |
> mistaken. |
| 13 |
|
| 14 |
This shouldn't be necessary when upgrading from qt 3.1.0 to 3.1.1. |
| 15 |
|
| 16 |
> |
| 17 |
> I've done this so much now that I've not ever bothered to check if |
| 18 |
> emerge can detect this... i.e. I upgrade from 3.0 to 3.1 QT, does emerge |
| 19 |
> know that I should recompile my KDE libs? (base/lib, and annything else |
| 20 |
> important). |
| 21 |
> |
| 22 |
> I wouldn't normally do this unless its required, as it takes so long :(, |
| 23 |
> so it would be great if emerge could suggest or warn me about it. |
| 24 |
|
| 25 |
The most we can do with the current portage featureset, and have done, is emit |
| 26 |
a warning message after qt is emerged. |
| 27 |
|
| 28 |
|
| 29 |
- -- |
| 30 |
Dan Armak |
| 31 |
Gentoo Linux developer (KDE) |
| 32 |
Matan, Israel |
| 33 |
Public GPG key: http://www.gentoo.org/~danarmak/danarmak-gpg-public.key |
| 34 |
-----BEGIN PGP SIGNATURE----- |
| 35 |
Version: GnuPG v1.2.1 (GNU/Linux) |
| 36 |
|
| 37 |
iD8DBQE+AfZ9UI2RQ41fiVERAoa7AJoDBhPBU3U+C7szFAhYAxjusDaSsgCeO4hM |
| 38 |
LBixL1gKcmPvOjOkTihPy5Y= |
| 39 |
=yENB |
| 40 |
-----END PGP SIGNATURE----- |
| 41 |
|
| 42 |
|
| 43 |
-- |
| 44 |
gentoo-dev@g.o mailing list |
Archives