From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 4.0.0 (2022-12-14) on finch.gentoo.org X-Spam-Level: *** X-Spam-Status: No, score=3.2 required=5.0 tests=DATE_IN_PAST_06_12,DMARC_NONE, FSL_HELO_NON_FQDN_1,HELO_NO_DOMAIN,INVALID_DATE,MAILING_LIST_MULTI, RDNS_NONE autolearn=no autolearn_force=no version=4.0.0 Received: from [213.242.186.232] (helo=fry) by cvs.gentoo.org with esmtp (Exim 3.30 #1) id 15qtQZ-0001Oy-00 for gentoo-dev@cvs.gentoo.org; Tue, 09 Oct 2001 03:43:55 -0600 Received: from fry (fry [127.0.0.1]) by fry (Postfix) with ESMTP id 7BDEEE6880 for ; Tue, 9 Oct 2001 11:43:23 +0200 (CEST) Subject: Re: [gentoo-dev] Final qt/QTDIR scheme From: Mikael Hallendal To: "Gentoo Dev." In-Reply-To: <200110090814.KAA12276@mailgw1.netvision.net.il> References: <200110090034.CAA09513@mailgw2.netvision.net.il> <1002597595.3475.16.camel@zoidberg> <200110090814.KAA12276@mailgw1.netvision.net.il> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-S5pgrNGfbCugNezYVtre" X-Mailer: Evolution/0.15 (Preview Release) Message-Id: <1002620603.8699.5.camel@fry> Mime-Version: 1.0 Sender: gentoo-dev-admin@cvs.gentoo.org Errors-To: gentoo-dev-admin@cvs.gentoo.org X-BeenThere: gentoo-dev@cvs.gentoo.org X-Mailman-Version: 2.0 Precedence: bulk Reply-To: gentoo-dev@cvs.gentoo.org List-Help: List-Post: List-Subscribe: , List-Id: Gentoo Linux development list List-Unsubscribe: , List-Archive: Date: Tue Oct 9 03:44:01 2001 X-Original-Date: 09 Oct 2001 11:43:22 +0200 X-Archives-Salt: d4c509ac-7773-4a38-8564-66e898d96499 X-Archives-Hash: 8ffc87eeb31b58206eb921cb3b650cf8 --=-S5pgrNGfbCugNezYVtre Content-Type: text/plain Content-Transfer-Encoding: quoted-printable 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=20 > developing GPL'd apps, or to purchase a license file, install it and deve= lop=20 > commercial ones. > qt-x11-free allows only the GPL part. It is essentially the same; this=20 > license is used e.g. for qt3 betas. I'm not going to add those to portage= , I=20 > 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 exam= ple,=20 > is also called qt-x11. That's why the ebuild is called qt-x11 too, and al= ways=20 > have been. There's no need to shorten names, that just creates confusion = :-).=20 > 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; th= at's=20 > where they are most useful. They might be though.=20 > But when I said: > - An app being compiled outside ebuilds, non-kde qt apps, and everything = else=20 > that doesn't use eclasses will have to trust that QTDIR is properly set, = or=20 > 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= =20 > 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 --=20 Mikael Hallendal Gentoo Linux Developer, Desktop Team Leader CodeFactory AB, Stockholm, Sweden --=-S5pgrNGfbCugNezYVtre Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQA7wsa6m0/ts8TQAWgRAgrSAKCriXqmrvD8ybiL56bhduejGCFDcACg397D vcdFnVO+hF/6TyYD1cro0GA= =fWmI -----END PGP SIGNATURE----- --=-S5pgrNGfbCugNezYVtre--