[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: On the matter of Qt packaging



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Donnerstag, 6. Februar 2003 15:40, Peter Mathiasson wrote:
> On Thu, Feb 06, 2003 at 01:01:15PM +0100, Ralf Nolden wrote:
> > The wisest thing to do IMHO is to prepare qt3 in a way that it works best
> > inside /usr/lib and /usr/bin while qt2, qt2e should be adapted and
> > reworked so they can still be used in parallel. That means, that sooner
> > or later one must find an agreement to use something like a QTDIR for
> > those packages. Martin got convinced now to use /usr/share/qt3 now for
> > qt-x11-free-3.1.1, so I would suggest /usr/share/qt2 for Qt 2.x,
> > /usr/share/qt2e for Qt-embedded 2.x and /usr/share/qt3e for Qt-Embedded
> > 3.x.
>
> Use /usr/bin/moc-qt2 with a link from /usr/share/qt2/bin/moc.
> ... no binaries in /usr/share.

I guess then renaming the binaries is the only alternative for qt 2. 

The only thing that would heavily simplify matters here is to have 
qt2-embedded and qt3-embedded be structured in the same way that qt2 and qt3 
are, so much that one can install the qt2-dev-tools or qt3-dev-tools which 
are provided by the x11 version and which work for the embedded versions as 
well (or package those up, too but leave the choice to use 

qt2e-dev-tools | qt2-dev-tools resp. qt3e-dev-tools | qt3-dev-tools

This way, only the qt2 binaries need to be renamed.

Ralf

>
> --
> Peter Mathiasson, peter at mathiasson dot nu, http://www.mathiasson.nu
> GPG Fingerprint: A9A7 F8F6 9821 F415 B066 77F1 7FF5 C2E6 7BF2 F228

- -- 
We're not a company, we just produce better code at less costs.
- --------------------------------------------------------------------
Ralf Nolden
nolden@kde.org

The K Desktop Environment       The KDevelop Project
http://www.kde.org              http://www.kdevelop.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE+QoHJu0nKi+w1Ky8RAgWJAJ4+akwQqvzUgMs9bd0eD1I/mjK1NACePlmB
i6Fdliqvzo8U5smfN1m4RFw=
=jjqQ
-----END PGP SIGNATURE-----




Reply to: