Simon Josefsson wrote:
> > * modules/csharpcomp: Depend on it.
> > * modules/javacomp: Depend on it.
>
> These two patches were forgotten, apparently.
Oops, fixed. Sorry, I'm constantly in a hurry these days.
> I'm now using csharpcomp to build the Libidn C# port.
>
> How does javacomp re
Simon Josefsson <[EMAIL PROTECTED]> writes:
> I think you could commit your patch to CVS meanwhile.
OK, I've done that, in both gnulib and coreutils.
___
bug-gnulib mailing list
bug-gnulib@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-gnulib
Bruno Haible <[EMAIL PROTECTED]> writes:
> I agree with all this. I've changed gnulib-tool to accept modules whose
> license is "GPLed build tool", and created a csharpcomp-script and
> javacomp-script module under this license. This should make it clear
> that - unlike the automake-provided build
Bruno Haible <[EMAIL PROTECTED]> writes:
> I agree with all this. I've changed gnulib-tool to accept modules whose
> license is "GPLed build tool", and created a csharpcomp-script and
> javacomp-script module under this license. This should make it clear
> that - unlike the automake-provided build
Simon Josefsson wrote:
> After including the csharpcomp module in libidn, I realized I don't
> need any of the C code in that module. I just need csharpcomp.sh.in,
> csharp.m4 and csharpcomp.m4.
>
> How about installing the following csharpcomp-script module for those
> files, and patching the csh
Simon Josefsson <[EMAIL PROTECTED]> writes:
> How about changing the License of the csharpcomp-script module to
> "helper-GPL", and make "helper-GPL" LGPL-compatible, as far as
> gnulib-tool is concerned?
To clarify: gnulib-tool should NOT alter the GPL license template in
csharpcomp.sh.in here.
