public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Torsten Veller <tove@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: License groups in ebuilds
Date: Sat, 12 May 2012 21:05:06 +0200	[thread overview]
Message-ID: <20120512202244.TAac5201.tv@veller.net> (raw)
In-Reply-To: <CAATnKFDhLmBJSd1VRfisaJTpEGQbmD4x39Da8hF3s3UM-q9i1Q@mail.gmail.com>

* Kent Fredric <kentfredric@gmail.com>:
> I'd welcome groups so we can have a "Perl_5" group. The lions share of
> modules published on CPAN are licensed "Under the same license as Perl
> 5 Itself", which implies "|| ( GPL-2 Artistic-1 )"

Perl is licensed as

| This program is free software; you can redistribute it and/or modify
| it under the terms of either:
|
| 	a) the GNU General Public License as published by the Free
| 	Software Foundation; either version 1, or (at your option) any
| 	later version, or
|
| 	b) the "Artistic License" which comes with this Kit.

The perl-module.eclass offers a default LICENSE as
LICENSE="${LICENSE:-|| ( Artistic GPL-1 GPL-2 GPL-3 )}"

So if a distribution uses "the same license as Perl 5 itself" you can
just drop the LICENSE from the ebuild (as long no former eclass sets its
own LICENSE).

I've further added comments to the LICENSE in the ebuilds if it does not
use "the same terms as the Perl 5 programming language system itself"
but "or-later" group of licenses (like GPL-2+ or Artistic+...).
-- 
Regards



  reply	other threads:[~2012-05-12 19:06 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-10  9:39 [gentoo-dev] License groups in ebuilds Ulrich Mueller
2012-05-10  9:57 ` Kent Fredric
2012-05-12 19:05   ` Torsten Veller [this message]
2012-05-12 19:12     ` [gentoo-dev] " Ciaran McCreesh
2012-05-12 19:49       ` Torsten Veller
2012-05-12 19:49       ` Ulrich Mueller
2012-06-16 17:49 ` [gentoo-dev] " Sebastian Pipping
2012-06-16 18:16   ` Ulrich Mueller
2012-09-14 23:35     ` Ulrich Mueller
2012-09-18  6:10       ` Ulrich Mueller

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20120512202244.TAac5201.tv@veller.net \
    --to=tove@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox