Re: [gentoo-dev] Final qt/QTDIR scheme

[Mikael Hallendal <hallski@gentoo.org>]

[-- Attachment #1: Type: text/plain, Size: 2765 bytes --]

tis 2001-10-09 klockan 10.10 skrev Dan Armak:
> On Tuesday 09 October 2001 05:19, you wrote:
> > 1) What are the difference between qt-x11 and qt-x11-free.
> qt-x11 comes under the QPL license. This allows to use it freely in 
> developing GPL'd apps, or to purchase a license file, install it and develop 
> commercial ones.
> qt-x11-free allows only the GPL part. It is essentially the same; this 
> license is used e.g. for qt3 betas. I'm not going to add those to portage, I 
> was just giving an example.

Sorry I was unclear, I was wondering what "feature"-changes there were
between the two. Or are they the exact same just distributed with
different licenses?

> > 2) Why is it called qt-x11 and not just 'qt'?
> >    I guess this is because you can build qt-embedded (Is that for
> >    framebuffer)? or perhaps there even is a qt-fb for that. Anyway, my
> >    point is, why not calling "regular" (x11) qt just plain and simple
> >    'qt' and use an extra ending for the others?
> Because qt-x11 is the full, proper name. The source archive/dir, for example, 
> is also called qt-x11. That's why the ebuild is called qt-x11 too, and always 
> have been. There's no need to shorten names, that just creates confusion :-). 
> It's like calling gnome, GDE.

Ok, didn't know the full name was qt-x11 (thought that someone named it
so in portage to make it more clear that it was the x11-build). What
this had to do with GNOME I dunno and why it would ever be called GDE.

> > When/if EClasses gets accepted they won't be restricted to KDE-use
> > (right?) and should probably be used for all qt-apps (and probably
> > others), meaning that if it's an qt2 app it inherits qt2.eclass and if
> > it's an qt3 app it inherits qt3.eclass.
> Er, wrong probably. Eclasses will not be used extensively outside kde; that's 
> where they are most useful. They might be though. 
> But when I said:
> - An app being compiled outside ebuilds, non-kde qt apps, and everything else 
> that doesn't use eclasses will have to trust that QTDIR is properly set, or 
> to set it manually to /usr/lib/qt-x11-$MAJOR_VERSION (no biggie)
> I forgot to mention that this is what *all* our ebuilds have had to do so 
> far. So we're still far better off.

Hmm .. if ebuilds will always just be used for KDE i can't see why it
should be added to portage. I think that if it works fine (which it
seems to do) and is accepted to be part of portage it should be utilized
wherever appropriate and IMHO it sounds like it would be in the examples
discussed above.

Anyway, it's your call, just curious.

Regards,
  Mikael Hallendal

-- 

Mikael Hallendal
Gentoo Linux Developer, Desktop Team Leader
CodeFactory AB, Stockholm, Sweden


[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]