| 1 |
On Saturday 02 July 2005 14:41, Gregorio Guidi wrote: |
| 2 |
> I'm back from a trip and I'm slowly catching up with all the mails on this |
| 3 |
> topic, but a couple of things come to my mind ... please bear with me. |
| 4 |
> |
| 5 |
> First, a new eclass for Qt4 ebuilds should really be called qt4.eclass, |
| 6 |
> with another one, qt3.eclass, to be used to port the current Qt3-based |
| 7 |
> ebuilds. Dealing with more than one major version in a single eclass is a |
| 8 |
> pain; this is mostly true for the kde eclasses, but still applies to Qt. |
| 9 |
> In fact, we need to introduce a new clean eclass for KDE4-based |
| 10 |
> applications, so starting from scratch with a kde4.eclass and a qt4.eclass |
| 11 |
> makes a lot of sense. |
| 12 |
|
| 13 |
I completely agree. |
| 14 |
|
| 15 |
> As many already pointed out, using something like |
| 16 |
> DEPEND="$(qt_min_version 3.1)" |
| 17 |
> is very ugly, so we should use it only if it is really unavoidable. |
| 18 |
|
| 19 |
I agree too, but I haven't seen yet how it can be avoided. |
| 20 |
|
| 21 |
> An application based on Qt4 should look just like this: |
| 22 |
> |
| 23 |
> inherit qt4 |
| 24 |
> |
| 25 |
> HOMEPAGE=... |
| 26 |
> SRC_URI=... |
| 27 |
> ... |
| 28 |
> |
| 29 |
> the qt4 eclass would automatically add a DEPEND="=x11-libs/qt-4*", and |
| 30 |
> would provide default src_compile(), src_install()... |
| 31 |
|
| 32 |
That's fine, except I would think that very few ebuilds would be able to make |
| 33 |
use of a default src_compile() and src_install(). It works for the kde |
| 34 |
eclass because most of the kde packages are built using the standard kde |
| 35 |
auto* scripts, but I doubt many qt only packages have the same build |
| 36 |
structure. |
| 37 |
|
| 38 |
[snip] |
| 39 |
|
| 40 |
While your proposal works okay for the qt4 scenario, I'm more concerned with |
| 41 |
the existing qt3 at the moment. As is, I stil l don't see a way around what |
| 42 |
has been proposed for those ebuilds. Until portage has the ability to handle |
| 43 |
&& deps, I fear there's no real way around it. I don't think we'll have time |
| 44 |
to wait much longer; I expect ebuilds that need qt4 will start appearing in |
| 45 |
portage soon and the minute that qt4 is marked ~arch it instantly creates the |
| 46 |
dependency mess addressed previously. |
| 47 |
-- |
| 48 |
gentoo-dev@g.o mailing list |
Archives