[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Separate csharpcomp.sh, and a license problem
From: |
Simon Josefsson |
Subject: |
Re: Separate csharpcomp.sh, and a license problem |
Date: |
Fri, 02 Dec 2005 11:13:21 +0100 |
User-agent: |
Gnus/5.110004 (No Gnus v0.4) Emacs/22.0.50 (gnu/linux) |
Simon Josefsson <address@hidden> 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. I feel the script should stay GPL. My point
is to make it possible to use the script to build LGPL material.
I also note that this is another situation where the AC_LIBSOURCES
approach appear to cause pains. If AC_LIBSOURCES was not used, it
would be simpler to have multiple gnulib-tool "instances" in the same
project, without having to write a configure.ac for each directory.
- Separate csharpcomp.sh, and a license problem, Simon Josefsson, 2005/12/01
- Re: Separate csharpcomp.sh, and a license problem,
Simon Josefsson <=
- Re: Separate csharpcomp.sh, and a license problem, Bruno Haible, 2005/12/02
- Re: Separate csharpcomp.sh, and a license problem, Simon Josefsson, 2005/12/02
- Re: Separate csharpcomp.sh, and a license problem, Bruno Haible, 2005/12/02
- Re: Separate csharpcomp.sh, and a license problem, Simon Josefsson, 2005/12/03
- Re: Separate csharpcomp.sh, and a license problem, Bruno Haible, 2005/12/05
- Re: Separate csharpcomp.sh, and a license problem, Simon Josefsson, 2005/12/06
- Re: Separate csharpcomp.sh, and a license problem, Simon Josefsson, 2005/12/03
- Re: Separate csharpcomp.sh, and a license problem, Bruno Haible, 2005/12/05
- Re: Separate csharpcomp.sh, and a license problem, Simon Josefsson, 2005/12/06
Re: Separate csharpcomp.sh, and a license problem, Ben Pfaff, 2005/12/02