Re: [Fwd: Re: [SLE] SuSE 8.2 copies already on sale at EBay]
You also seem to think that since YaST is on the same CDs as >software that is GPL, then YaST must also be GPL - not so in the slightest,
Also true. But how was YaST created? Was GCC used? Or did SuSE create their own compiler/interpreter for this?
It doesn't matter. The output (in this case the YaST binary) of GPL >programs is NOT required to be GPL unless the output contains part of the GPL program.
I'm not sure about that. Was the YaST binary created by linking in glibc? If so, and the source code called a function like printf(), then it should be part of the GPL. ~~Nick _______________________________________________ Join Excite! - http://www.excite.com The most personalized portal on the Web!
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, On Sunday 13 April 2003 22:30, Nicholas Parsons wrote:
I'm not sure about that. Was the YaST binary created by linking in glibc? If so, and the source code called a function like printf(), then it should be part of the GPL.
Nope, glibc is released under the LGPL not the GPL. - -- Cheers, Chris Howells -- chris@chrishowells.co.uk, howells@kde.org Web: http://chrishowells.co.uk, PGP ID: 33795A2C KDE: http://www.koffice.org, http://printing.kde.org, http://usability.kde.org -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2-rc1-SuSE (GNU/Linux) iD8DBQE+mdh3F8Iu1zN5WiwRAp6mAJoDvXxteNjM720iMYVc1W2O997OagCgjbkY tABcG3oHAtuRH1rp0FxCH0g= =9gFD -----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On April 13, 2003 05:30 pm, Nicholas Parsons wrote:
I'm not sure about that. Was the YaST binary created by linking in glibc? If so, and the source code called a function like printf(), then it should be part of the GPL.
Nice try, glibc is lgpl'ed. Charles - -- "Linux, because up-time matters gawk; talk; date; wine; grep; touch; unzip; touch; gasp; finger; gasp; mount;\ fsck; more; yes; gasp; umount; make clean; make mrproper; sleep." - --Drunken Bastard -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE+mdwd3epPyyKbwPYRAsNPAJ92xyo4XgC4AYubbNMwkZBfkYZlkQCgoXG4 KShm4V8fZtTd06sZjxyaPJY= =SSSZ -----END PGP SIGNATURE-----
On Sunday 13 April 2003 22:52, Charles Philip Chan wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On April 13, 2003 05:30 pm, Nicholas Parsons wrote:
I'm not sure about that. Was the YaST binary created by linking in glibc? If so, and the source code called a function like printf(), then it should be part of the GPL.
Nice try, glibc is lgpl'ed..
Let me get this straight - if I write a program which is linked against a library, my program could be governed by the library's licence? I can see this would be the case if static linked, but surely not for a dynamically linked library? Dylan -- Sweet moderation Heart of this nation Desert us not We are between the wars - Billy Bragg
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, On Sunday 13 April 2003 23:07, Dylan wrote:
Let me get this straight - if I write a program which is linked against a library, my program could be governed by the library's licence? I can see
Sure. The LGPL however specifically allows propreitary software to link against it.
this would be the case if static linked, but surely not for a dynamically linked library?
It doesn't make any difference I don't think -- it's still linked against it. - -- Cheers, Chris Howells -- chris@chrishowells.co.uk, howells@kde.org Web: http://chrishowells.co.uk, PGP ID: 33795A2C KDE: http://www.koffice.org, http://printing.kde.org, http://usability.kde.org -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2-rc1-SuSE (GNU/Linux) iD8DBQE+meM9F8Iu1zN5WiwRAgWwAKCUI2E77DZ3PjLaB4Gaij9S5zhNuACggFH4 ff7P3dTNgrXoJQQ02lmFU1Y= =0/q2 -----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On April 13, 2003 06:07 pm, Dylan wrote:
Let me get this straight - if I write a program which is linked against a library, my program could be governed by the library's licence? I can see this would be the case if static linked, but surely not for a dynamically linked library?
No, it not governed the library licence if the library is lgpl'ed. lgpl means you can link proprietary code or code under a gpl incompatible licence with the library without changing the licence of you software. For further info, please refer to: http://www.gnu.org/copyleft/lesser.html Charles - -- "Linux, because up-time matters gawk; talk; date; wine; grep; touch; unzip; touch; gasp; finger; gasp; mount;\ fsck; more; yes; gasp; umount; make clean; make mrproper; sleep." - --Drunken Bastard -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE+meNB3epPyyKbwPYRAg4HAJ9Hp/SD2zvAt2aAU0JaxNwITemcoACdHXdk TCyeg4PQ4EVI/UDc2gLMr8o= =jtmR -----END PGP SIGNATURE-----
participants (4)
-
Charles Philip Chan -
Chris Howells -
Dylan -
Nicholas Parsons