[gentoo-dev] Questions (qt3, kde3, and misc) - please answer

[gentoo-dev] Questions (qt3, kde3, and misc) - please answer

[Dan Armak]

Hi all, 

My questions remain unanswered, probably because they're in a thread called 
"final qt/QTDIR scheme". So I'm reposting here. This is a better verion of 
the questions anyway.

0. How do I define a dependency lilke
3.0.0>x11-libs/qt-x11>=2.3.1-r2
Since qt major versions are api-incompatible, I ned a specific major version 
and a >= for a minor version. Hope I'm making myself clear :-)

I could make two deps:
<x11-libs/qt-x11-3.0.0
>=x11-libs/qt-x11-2.3.1-r2

But the first could be satisfied by 2.2 and the second by 3.0 and I wouldn't 
get the right thing.

I remember reading comments in portage.py about "*" dependencies, when are 
they coming?

What should I do for now?

1. If I do set
DEPEND=">=x11-libs/qt-x11-2.3.1-r1 <x11-libs/qt-x11-3.0.0_beta6"
then, emerge will emerge both these packages, each for the other's 
dependency. It is not smart enouh to see that the deps can be satisfied with 
just one. This is a little off topic, just a note.

2. If I do succeed in making such dependencies, should I (via eclasses) 
require all kde/qt apps to depend on >=qt-x11-2.3.1-r2, which is the current 
revision and is the one that introduces the new QTDIR coexistence scheme?

Many people probably have qt 2.3.0 or 2.2.3 installed, which in fact fulfill 
the kde dependencies. And if they are forced to go from 2.2.x to 2.3.x 
they'll have to recompile all of their kde/qt apps, as the revisions are not 
binary compatible. Of course, with the new scheme, I can easily have 2.2 and 
2.3 revision coexist as well. Should I? That would mean manually emerging the 
new revision of the qt version you already have, as the old revisions aren't 
coexistence-compatible.

2.5. Should I make everyone upgrade to the new revision of qt2.x before 
emerging qt3.x? And if I should, how?
If they don't upgrade, I cannot guarantee successful emerging of anything 
qt-dependant.

3. The decision has been taken not to include pre-final kde (and qt) versions 
in portage, not even masked. However, many people are likely to be interested 
in the upcoming kde3 ebuilds (kde3-alpha1 was released recently; the ebuilds 
will be ready as soon as this qt thing is finished). On person has already 
asked me for copies of these ebuilds, others may as well. Suggestions for 
placing and distributing them? (Before you suggest it, I don't have a site).

4. A question for the FHS experts: what is the right place to install 
secondary (or equal) copies of KDE? Only one copy can live in /usr, as the 
filenames don't change between releases. /opt/kdeX.Y?

-- 

Dan Armak
Gentoo Linux Developer, Desktop Team
Matan, Israel