Thanks - that's the conclusion I came to as well.
> -Original Message-
> From: Merrill Cornish [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, January 19, 2005 4:15 PM
> To: Craig Andera; nant-users@lists.sourceforge.net
> Subject: Re: [Nant-users] GPL and buil
Craig,
I'm pretty sure that "link" means _link_. If you go to the FSF site, in their
explanation of the GPL (at least at one time), they gave the example of the
GPL'ed Bash application being used to call proprietary programs (which is much
like NAnt calling external programs). Since the Bash
I'm not a lawyer, but my understanding of the GPL is that any component that
links to a GPL program must also release under the GPL. The obvious example
of this in Nant is tasks. However, I'm trying to figure out if the same
applies to my build script. Although it's XML, it could still be considere
ohn Hardin
> Sent: Wednesday, 19 January 2005 7:26 AM
> To: [EMAIL PROTECTED]
> Cc: NAnt Users mailing list
> Subject: Re: [Nant-users] GPL and build scripts
>
>
> On Tue, 2005-01-18 at 10:47, [EMAIL PROTECTED] wrote:
>
> > Can anyone provide guidance here? Is my build sc
On Tue, 2005-01-18 at 10:47, [EMAIL PROTECTED] wrote:
> Can anyone provide guidance here? Is my build script constrained to be GPL
> the way tasks would be?
Nope, no more than a shell script running under BASH is bound by the GPL
on BASH.
IANAL either, though.
--
John Hardin
Development and Te
I'm not a lawyer, but my understanding of the GPL is that any component that
links to a GPL program must also release under the GPL. The obvious example
of this in Nant is tasks. However, I'm trying to figure out if the same
applies to my build script. Although it's XML, it could still be considere
