| 1 |
Clarification: suppose someone has kde-2.1.1 and wants to emerge |
| 2 |
kdenetwork-2.1.1, which he doesn't have. |
| 3 |
|
| 4 |
If I do nothing at all to the old KDE ebuilds, he'll be able to do it |
| 5 |
successfully. However, if he updates his qt to a new, multi-qt supporting |
| 6 |
versoin, he will only be able to emerge inheriting ebuilds, since appropriate |
| 7 |
parameters to configure are needed which are supplied by kde.eclass. The same |
| 8 |
goes for multi-kdelibs. |
| 9 |
|
| 10 |
Actually, he *might* be able to use non-inheriting ebuilds with multi-*, buyt |
| 11 |
he might not. Depends on the configuration. It's best and safest and surest |
| 12 |
to upgrade. After all kde-2.1.x is pre-rc6 stuff. |
| 13 |
|
| 14 |
-- |
| 15 |
|
| 16 |
Dan Armak |
| 17 |
Gentoo Linux Developer, Desktop Team |
| 18 |
Matan, Israel |
Archives