RE: License in the Mac installer

ginal Message- | From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Manuel M T Chakravarty | Sent: 12 February 2008 05:56 | To: cvs-ghc@haskell.org | Subject: License in the Mac installer | | Mac installer packages usually present a license to the user to accept | during the install

Re: License in the Mac installer

Roman Leshchinskiy: Manuel M T Chakravarty wrote: Roman Leshchinskiy: It would be possible to distribute GHC itself under BSD3 and readline under the GPL if they were really distributed as two independent thing (and, e.g., optionally linked together during installation). But by prelinkin

Re: License in the Mac installer

to be very precise, I think that the entire distribution is licensed under the intersection of BSD3-for-GHC and GPL-for-everything. Now, this only affects what copyright notices need to stay included (any further restriction would obviously violate the GPL). Also, as far as I can tell, as lo

Re: License in the Mac installer

Manuel M T Chakravarty wrote: Roman Leshchinskiy: It would be possible to distribute GHC itself under BSD3 and readline under the GPL if they were really distributed as two independent thing (and, e.g., optionally linked together during installation). But by prelinking them, you have created

Re: License in the Mac installer

Bryan O'Sullivan: Manuel M T Chakravarty wrote: By all means get legal advice. However, I am curious, what exactly is it in my reasoning that you do not agree with? Essentially, that it is possible to combine GPL and BSD works and distribute the combined result under the BSD license. Surely

Re: License in the Mac installer

Roman Leshchinskiy: Manuel M T Chakravarty wrote: * You can link a BSD3 program with a GPL'ed library and distribute the result. (This opinion is supported by the FSF listing BSD3 as a GPL-compatible license on their web pages and this item in their licensing FAQ:

Re: License in the Mac installer

R Hayes: On Feb 12, 2008, at 8:50 PM, Manuel M T Chakravarty wrote: * Whether you link statically or dynamically against a GPL'ed library does not make any difference as far as your legal obligations are concerned. (This opinion is supported, eg, by the following item in the FSF's licensin

Re: License in the Mac installer

On Feb 12, 2008, at 8:50 PM, Manuel M T Chakravarty wrote: * Whether you link statically or dynamically against a GPL'ed library does not make any difference as far as your legal obligations are concerned. (This opinion is supported, eg, by the following item in the FSF's licensing FAQ:

Re: License in the Mac installer

Manuel M T Chakravarty wrote: > By all means get legal advice. > > However, I am curious, what exactly is it in my reasoning that you do > not agree with? Essentially, that it is possible to combine GPL and BSD works and distribute the combined result under the BSD license. > PS: Once the new e

Re: License in the Mac installer

FWIW, here are my two kopeks. Manuel M T Chakravarty wrote: * You can link a BSD3 program with a GPL'ed library and distribute the result. (This opinion is supported by the FSF listing BSD3 as a GPL-compatible license on their web pages and this item in their licensing FAQ:

Re: License in the Mac installer

Bryan O'Sullivan: Manuel M T Chakravarty wrote: By offering GHC under BSD3, we do allow people to distribute it under the GPL and hence fullfil our obligations under the GPL (which we incurred by linking - in whatever way - against readline). Does that clarify the point? I believe that

Re: License in the Mac installer

Manuel M T Chakravarty wrote: > By offering GHC under BSD3, we do allow people to distribute > it under the GPL and hence fullfil our obligations under the GPL (which > we incurred by linking - in whatever way - against readline). Does that > clarify the point? I believe that this claim is not a

Re: License in the Mac installer

Thorkil Naur: On Tuesday 12 February 2008 06:56, Manuel M T Chakravarty wrote: Mac installer packages usually present a license to the user to accept during the installation process. Consequently, I added what I think is a correct licensing document to the tree at http://darcs.haskell.org/

Re: License in the Mac installer

Hello, On Tuesday 12 February 2008 06:56, Manuel M T Chakravarty wrote: > Mac installer packages usually present a license to the user to accept > during the installation process. Consequently, I added what I think > is a correct licensing document to the tree at > >http://darcs.haskell.

License in the Mac installer

Mac installer packages usually present a license to the user to accept during the installation process. Consequently, I added what I think is a correct licensing document to the tree at http://darcs.haskell.org/ghc/distrib/MacOS/installer-docs/ license.html However, this is of course a