1 |
On Tue, 20 Jun 2006 19:29:10 +0200 |
2 |
"Diego 'Flameeyes' Pettenò" <flameeyes@g.o> wrote: |
3 |
|
4 |
> On Tuesday 20 June 2006 19:10, Joshua Jackson wrote: |
5 |
> > I don't want to go down the path again of having two nearly |
6 |
> > identical flags for a different slotted version of a framework. I'd |
7 |
> > like to see just qt with a maintainer deciding if its going to be |
8 |
> > qt3 or qt4. |
9 |
> Unfeasible. GTK 1.2 was deprecated when the two flags were merged, |
10 |
> Qt3 is all but deprecated right now. If you decide to use just one |
11 |
> version of qt, it would be qt3 for all, and a mess when KDE 4 will |
12 |
> come out, we can't think of NOT having time for the change from 3.x |
13 |
> to 4. |
14 |
> |
15 |
> Also, gtk and gtk2 flags did NOT work as I asked, gtk2 was to enable |
16 |
> gtk2 version when both a 1.2 and 2 version was available, so for |
17 |
> instance ethereal +gtk -gtk2 built gtk 1.2, and -gtk +gtk2 built |
18 |
> NOTHING. What I'm asking is for qt3 enable the qt3 version, qt4 the |
19 |
> qt4 version, qt3 and qt4 both if possible (that is usually the case |
20 |
> for stuff that has both version available, as one does not obsolete |
21 |
> the other right now). |
22 |
|
23 |
I don't mind the qt3/qt4 flags for packages that support both, but could |
24 |
we also have a qt flag that selects the "preferred" version (or for |
25 |
packages that only support one)? Many people simply don't care about the |
26 |
version but also don't need support for both in every package, also |
27 |
that makes transition easier IMHO. |
28 |
Though that creates a problem when both the unversioned and one of the |
29 |
versioned flags are used, not sure how to deal with that. |
30 |
|
31 |
Marius |
32 |
|
33 |
-- |
34 |
Public Key at http://www.genone.de/info/gpg-key.pub |
35 |
|
36 |
In the beginning, there was nothing. And God said, 'Let there be |
37 |
Light.' And there was still nothing, but you could see a bit better. |