site_archiver@lists.apple.com Delivered-To: darwin-dev@lists.apple.com Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=aI2Bn2MpXhVS37FDDXTTXvRb1Zx/rFfMxYn5+gDRDTNhkzQs8qfgCAo/A+2Ho6aOt2r+IavFSa/Ul/e1n3/kZN6XpAu24qUukFKa4oCG3yd2e/xwULpkV4g+j6cm7/BRZOHJXGihzbpxRy7IVc7J99GGDqfvwjr7WnO0jUDZGNE= On 5/8/05, Peter O'Gorman <peter@pogma.com> wrote:

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

David Leimbach wrote:

| | The GPL creates business problems that the BSDL [and LGPL in this | case] does not. It goes beyond "philosophy". The fact is libedit is | designed to replace libreadline. So the symlink makes perfect | technical sense. The problem is it doesn't offer 100% libreadline | compatiblity yet.

This is totally beside the point. No other *BSD ships a libreadline in /usr/lib that links to libedit. FreeBSD ships GNU readline, NetBSD only has libedit in /usr/lib (but it does have /usr/include/readline/readline.h and /usr/include/readline/history.h). The problem is not that libedit does not offer 100% GNU readline compatibility, it is that Apple sees fit to pretend that it does by including the symlink.

| | You are free to install and link against libreadline if you choose. | Alternatively you could hack on libedit [probably not what you want to do :)].

This is crap, it is far easier for a user who wishes to do so to link ~/lib/libreadline.dylib to /usr/lib/libedit.dylib than it is to remove the link.

| | Claiming that the symlink has no purpose is a bit subjective I'd say. | For me I'd want software that CAN link libedit instead of libreadline | to link libedit instead. To me that symlink saves me a lot of crap of | fixing the project I wanted to build/link to use the correct library. | I agree it's ugly and that it's a workaround but good luck getting | every project that fits that pattern to bend to your will.

See above. You could easily put such a link in the build dir.

1) This is Darwin not *BSD 2) Symlinks suck in general 3) Adding a symlink to a build or home directory doesn't address the problem of software distribution at all, which is likely why apple chose the path they did. The GPL only comes into play when you redistribute. They claimed it was a license issue already. None of your suggestions solve their problem. The only current solution is to build libreadline if you want it, install it elsewhere, and use it. Unless apple can be persuaded to "fix" what some people see as a problem [and I really don't care... it doesn't bother me] this will likely remain the only choice and further discussion probably won't help the situation at all. Dave

Peter - -- Peter O'Gorman - http://www.pogma.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (Darwin)

iQCVAwUBQn7jW7iDAg3OZTLPAQJtFwP+O5dbz5AvzJQg54+vlGZiPt2N/+ute8/h 0kBIDdLxviO7j3vZtnUWHpUKh0NINBA06cSMF2QuQ0DNA16tZtMTr0KwtRUGKM+w BgA3f5g6Rez/bxwZcKnPYLKW8nlzXfg9WqnDPhVyzCaa7FUQAOHW+wBQvJTHM3/R E/tLI00rp3k= =1CG0 -----END PGP SIGNATURE-----

_______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-dev mailing list (Darwin-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-dev/site_archiver%40lists.appl... This email sent to site_archiver@lists.apple.com