Does it really make sense to have all of QT hidden away in /usr/qt4 ? I
was expecting at least some things like include files or libraries to be
under /usr/include and /usr/lib respectively.
My concern is how are autoconf, and the like, scripts that need to find
QT libraries and includes going to find it ? Are we expecting that
everyone will know to do something like this:
./configure --with-qt-include=/usr/qt4/4.4.1/include \
--with-qt-libs=/usr/qt4/4.4.1/lib/
Is there no pkg-config .pc file for QT that can be placed in
/usr/lib/pkgconfig to help with this ?
Is this the common layout on Linux based distributions where GNOME is
considered the primary desktop rather than KDE ? What is they layout
when KDE is the primary desktop ?
> This Fasttrack proposes an overall "Uncommitted" Interface
> Stability Classification for QT4. Considering the ABI Micro
> Release Stability guarantee provided by Trolltech ASA, a
> "Committed" Interface Stability Classification would have been
> appropriate. However, QT4's dependency on
> External/Evolving/Uncommitted Interfaces makes an overall
> "Committed" Interface Classification inaproppriate.
That doesn't follow. Just because you have lower classified
dependencies doesn't mean you can't be higher than them. That is the
definition of what we do in ARC. Everything is built on something of a
lower classification at some level. So if this really could be
Committed other than for the incorrect assumption on the dependencies it
should be Committed.
OpenSSL is not Uncommitted it is "Contracted External".
--
Darren J Moffat
