Thomas Klausner <thomasklausner%users.sourceforge.net@localhost> writes: > On Wed, Apr 15, 2009 at 08:25:16AM +0200, Guillaume Lasmayous wrote: >> wip/castget is almost ready, apart from the license: >> castget is "dual-licensed", LGPL for the libraries, and GPL for the >> rest. How should this be handled ? Two different packages, even if the >> are extremely small ? The word "dual-licensed" usually refers to code where one can choose to distribute it under one of two licenses, typically BSD and GPL, in order to be friendly to both BSD and Linux kernels. Here, I think you're talking about a package which contains code under two licenses, which is aggregation, not dual licensing. > The infrastructure will get support for adding dependencies on more > than one license soon. Then you just add them both in the > LICENSE... for now, just comment it out (something like > #LICENSE= gnu-lgpl-v2.1 AND gnu-gpl-v2 > or whatever it is exactly). And in this case, since LPGL is strictly more liberal than GPL, you can reasonably write LICENSE= gnu-gpl-v2 along with the commented out future value without harming anyone.
Attachment:
pgpdQ5cwo1M23.pgp
Description: PGP signature
------------------------------------------------------------------------------ Register Now & Save for Velocity, the Web Performance & Operations Conference from O'Reilly Media. Velocity features a full day of expert-led, hands-on workshops and two days of sessions from industry leaders in dedicated Performance & Operations tracks. Use code vel09scf and Save an extra 15% before 5/3. http://p.sf.net/sfu/velocityconf
_______________________________________________ pkgsrc-wip-review mailing list pkgsrc-wip-review%lists.sourceforge.net@localhost https://lists.sourceforge.net/lists/listinfo/pkgsrc-wip-review