public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mikael Hallendal <micke@codefactory.se>
To: gentoo-dev@cvs.gentoo.org
Subject: Re: [gentoo-dev] Final qt/QTDIR scheme
Date: Mon Oct  8 21:22:02 2001	[thread overview]
Message-ID: <1002597595.3475.16.camel@zoidberg> (raw)
In-Reply-To: <200110090034.CAA09513@mailgw2.netvision.net.il>

tis 2001-10-09 klockan 02.34 skrev Dan Armak:
> Hi all,

Hi!

> The current and (I very much hope) final scheme is this:
> qtX installs in /usr/lib/${P}. This is qt-x11-${PV} normally. However there 
> are also qt-x11-free and qt-embedded libraries which we may have in the 
> future, so we don't use /usr/lib/qt-${PV} anymore. A symlink is created in 
> /usr/lib/qt-x11-$MAJOR_VERSION. That is, for now, 2 or 3.

A few questions:

1) What are the difference between qt-x11 and qt-x11-free.

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?

> 99% of qt apps are also KDE apps and as such use eclasses. A configure script 
> should automatically use the qt in QTDIR, which is by default the latest qt. 
> Therefore, once kde3 is out, I will make (tiny) qt{2,3}.eclass files that 
> will say QTDIR=/usr/lib/qt-x11-$MAJOR_VERSION. kde.eclass itself will have 
> QTDIR set to the latest version available.

> - 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).

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. 

Regards,
  Mikael Hallendal

> Well, that's it. I'm writing this late at night, so I've probably said 
> something stupid. Comments welcome!

Written even later :)

-- 
Mikael Hallendal                micke@codefactory.se
CodeFactory AB                  http://www.codefactory.se/
Office: +46 (0)8 587 583 05     Cell: +46 (0)709 718 918




  reply	other threads:[~2001-10-09  3:21 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-08 18:35 [gentoo-dev] Final qt/QTDIR scheme Dan Armak
2001-10-08 21:22 ` Mikael Hallendal [this message]
2001-10-09  2:14   ` Dan Armak
2001-10-09  3:44     ` Mikael Hallendal
2001-10-09  4:08       ` Dan Armak
2001-10-09  5:43         ` Mikael Hallendal
2001-10-09  8:19 ` [gentoo-dev] Final qt/QTDIR scheme - Dan Armak
2001-10-09  8:28   ` Mikael Hallendal
2001-10-09  9:15   ` [gentoo-dev] Final qt/QTDIR scheme - even more questions Dan Armak
2001-10-09 15:34     ` Mikael Hallendal
2001-10-09 16:16 ` [gentoo-dev] Final qt/QTDIR scheme - solution Dan Armak
2001-10-09 17:58   ` Daniel Robbins
2001-10-09 18:37     ` Mikael Hallendal
2001-10-10 11:38     ` Dan Armak

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1002597595.3475.16.camel@zoidberg \
    --to=micke@codefactory.se \
    --cc=gentoo-dev@cvs.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox