hi tom,
i believe it's not source
code alone, my program must not link to nant binaries either. even if that's not
a problem for me now, i can imagine scenarios where it might become one, namely
the nant/installer stuff i mentioned. i understand that i can not include nant
binaries with my proprietary software and call nant methods to perform tasks
that, for instance, create IIS directories. is this correct?
similar problem with user tasks. they have to link to
nant and therefore cannot be closed-source if nant is under the GPL license,
right? personally, i don't see the benefits of not sharing the source code of
tasks, but the nant developers have to make the decision whether they actually
want to use a license that makes this impossible. (especially considering
potential msbuild compatibility.)
then again, it might be possible to choose a license
that allows the two scenarios i described above without allowing closed-source
modifications and extensions of nant itself. lesser GPL maybe?
stefan
Von: Jordan, Tom
[mailto:[EMAIL PROTECTED]
Gesendet: Mo 10.11.2003 22:08
An: Wenig, Stefan; '[EMAIL PROTECTED]'
Betreff: RE: [nant-dev] Licensing
Gesendet: Mo 10.11.2003 22:08
An: Wenig, Stefan; '[EMAIL PROTECTED]'
Betreff: RE: [nant-dev] Licensing
Hi Stefan:
> -----Original Message-----
> From:
Wenig, Stefan [mailto:[EMAIL PROTECTED]]
>
Sent: Thursday, November 06, 2003 3:04 AM
> To:
[EMAIL PROTECTED]
> Subject: [nant-dev]
Licensing
>
> it also says to me as a potential NAnt user: if you
want to charge for
> your software *and* use NAnt, this product's license
goes out
> of its way
> to make this harder.
>
This is
incorrect.
AFAICT, The GPL makes zero claims on the outputs of
a
tool. The gcc project goes so far as to state such
in order to
alleviate the concern. You can use nant
to build commercial products as
long as your product
does not contain any nant source code.
--
Tom.
