[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH] Support for multiple licenses.
From: |
Alexandre Duret-Lutz |
Subject: |
Re: [PATCH] Support for multiple licenses. |
Date: |
Sat, 14 Jun 2003 19:40:48 +0200 |
User-agent: |
Gnus/5.1002 (Gnus v5.10.2) Emacs/21.3 (gnu/linux) |
>>> "Sergey" == Sergey Poznyakoff <address@hidden> writes:
Sergey> Hello,
Sergey> When copying required files, automake in its current form supposes
Sergey> that the package being 'automade' falls under the terms of only
Sergey> one license (either GPL or Lesser GPL). However, some packages
Sergey> are distributed under the terms of the two licenses. For example,
Sergey> GNU Mailutils package distributes its libraries under LGPL, and
Sergey> binary programs under GPL. Thus, in Mailutils we need both COPYING
Sergey> and COPYING.LIB to be distributed.
That should not be a problem. Just copy both files into your
top-level directory and they will be distributed.
Sergey> I propose to add a new switch 'multiple-licenses' which would tell
Sergey> automake that the package needs both files. Then, if one sets in the
Sergey> Makefile.am
Sergey> AUTOMAKE-OPTIONS = gnu multiple-licenses
Sergey> and copies COPYING.LIB to the root directory of his package, then
Sergey> automake will add both COPYING and COPYING.LIB to the DIST_COMMON
Sergey> variable of the resulting Makefile.in.
I'm not sure I understand the logic. If users still have to
copy COPYING.LIB, what's wrong if they need to copy COPYING too?
Saving one copy doesn't seem worth an additional option.
Especially because adding licenses to a project is usually done
only once.
--
Alexandre Duret-Lutz