Reason for -no-stl in qt-copy configure recommendation?

[Neil Stevens]

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

On Tuesday April 29, 2003 02:49, David Faure wrote:
> On Tuesday 29 April 2003 23:03, Neil Stevens wrote:
> > On Tuesday April 29, 2003 04:25, Daniel Stone wrote:
> > > glib (was the decision made to pull it in to kdesupport?)
> > > and quite a few other *EXTERNAL* libs.
> >
> > aRts 1.1 still works, which doesn't use glib.  The glib-using aRts 1.2
> > is optional.
>
> ... until the first arts-1.2 feature becomes needed in kdelibs.
> Do you really want to maintain your own fork of arts? Strange decision.
> (I'm just curious about this, I don't care either way).

Personally, I'd rather not see kdelibs require aRts anymore than it 
currently does.  It's highly likely that for KDE 4 we'll be dropping aRts, 
so we shouldn't add anything new that will just need rewritten when the 
time comes.

Even so, I'd be very surprised if KNotify or libartskde had new 
requirements on aRts 1.2.  If such requirements popped up, sure, I'd 
reconsider.  But I don't expect it to happen.

> And obviously everyone will be using arts-1.2 (distributors and users),
> so I don't think this statement has much relevance anyway.

Anyone who feels like installing GNOME might, sure.  But that's their 
choice.  Nothing in KDE forces them to do that.

- -- 
Neil Stevens - neil at qualityassistant.com
"The shepherd drives the wolf from the sheep's throat, for which the
sheep thanks the shepherd as a liberator, while the wolf denounces him
for the same act as the destroyer of liberty." -- Abraham Lincoln
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE+rvqJf7mnligQOmERAn24AJ4t2M8DPX7SrmK6CBdHcPk+9v23uQCglaFm
yNqFZx8bNTl5bIkDAf3li3U=
=CXYa
-----END PGP SIGNATURE-----