From kde-core-devel  Tue Jul 29 20:50:39 2003
From: Rob Kaper <cap () capsi ! com>
Date: Tue, 29 Jul 2003 20:50:39 +0000
To: kde-core-devel
Subject: Re: Qt 3.2 requirement
X-MARC-Message: https://marc.info/?l=kde-core-devel&m=105951277012817
MIME-Version: 1
Content-Type: multipart/mixed; boundary="--jsrFa/5v3cIbBmG8"


--jsrFa/5v3cIbBmG8
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Tue, Jul 29, 2003 at 10:33:28PM +0200, Guillaume Laurent wrote:
> Marc, you couldn't be more wrong. I've been confronted to this situation =
many=20
> times, both on my personal projects and at work. The *only* good reason t=
o=20
> support several versions of a library is because your users require it.=
=20
> Otherwise you don't, because there's nothing but trouble there.

Forward, backward and akward compatibility is probably the number one user
request for any serious software project.

Yes, it's trouble, or at least will require more work, foresight and
insight. But that's why we are computer programmers: we create tools for
users often knowing they can not create those tools for themselves, and
since compatibility issues are important to users, we make that one of our
own priorities.

The question is not whether supporting multiple library versions is a good
thing. It is. The question is whether it is worth the effort. I'd say it is.

If we decide it's not, I'm all in favor of removing any admin/ hack that
causes more work to maintain and dramatically increases package sizes
(especially for smaller stand-alone projects).

Rob
--=20
Rob Kaper     | "They that can give up essential liberty to obtain a little
cap@capsi.com | temporary safety deserve neither liberty nor safety."
www.capsi.com | - Benjamin Franklin, Historical Review of Pennsylvania, 1759

--jsrFa/5v3cIbBmG8
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE/Jt4etppIl2G1SjcRAk+EAJ9HHDZHEO1/VUvoOzrqkmzdLuoQYwCbBZtC
dBVltIkOI3IpO4UsFJvzNyA=
=9JDF
-----END PGP SIGNATURE-----

--jsrFa/5v3cIbBmG8--