From: Giovanni Biscuolo <g@xelera.eu>
To: zimoun <zimon.toutoune@gmail.com>, Tobias Geerinckx-Rice <me@tobias.gr>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Perl modules dual licensing (was Re: Bioconductor package flowPeaks license Artistic 1.0?)
Date: Fri, 20 Dec 2019 11:24:37 +0100 [thread overview]
Message-ID: <87k16r70re.fsf@roquette.mug.biscuolo.net> (raw)
In-Reply-To: <CAJ3okZ1jgxEKHabDYW8wC5jEqUd3vpyQ6jnMmtGtXVd6OUwTXA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2178 bytes --]
Hi zimoun
zimoun <zimon.toutoune@gmail.com> writes:
[...]
> Where is the License of Perl 5 and below explicitly defined? There is
> no pointer...
Ricardo pointed you to https://dev.perl.org/licenses/, that is a web
version of this
https://perl5.git.perl.org/perl5.git/blob/HEAD:/README
Perl is dual licensed at least since 1994-10-17 (see the README history
[1]
> What I understand is: when the License of Perl 5
There is no "License of Perl 5", it is Perl 5 that is dual licensed
The same dual license scheme is usually (usually?!?) adopted by Perl
modules, at least those on CPAN
http://www.cpan.org/misc/cpan-faq.html#How_is_Perl_licensed
> and below is used, then the copyright holder chooses either the
> Artistic 1.0, either the GPL. Then the License of Perl 5 and below is
> free but non-copyleft.
Since there is no "License of Perl 5" that license cannot be qualified
:-)
> Well, it appears to me a hack. I guess that there is a lot of Perl
> packages under Artistic 1.0 which seems an issue.
I don't know how many packages/modules are distributed only using
Artistic License 1.0, but please consider that as I said above that
*many* are dual licensed.
The fact that Perl modules are (must?) commonly dual licensed is
somewhat a mystery to me, but I do not care :-D
> So let create this License of Perl 5 and below saying: choose between
> Artistic 1.0 or GPL. And because you have this choice, everything is
> fine.
>
> I probably misread
No, you do not misread: dual licensing is used in many situation and is
non a "hack", it's the decision of the copyright holder to allow
different legal uses of the software
In this particular case, **fortunately** the dual licensing was adopted
"since the beginning" to fix the problems with Artistic License
[...]
Last things about names: since Oct 2019 [2] Perl 5 is Perl (Perl 4 is
gone long ago) and Perl 6 is Raku, so finally there is no more need to
say "Perl 5" :-)
Ciao! Gio'
[1] https://perl5.git.perl.org/perl5.git/history/HEAD:/README
[2] https://lwn.net/Articles/802329/
--
Giovanni Biscuolo
Xelera IT Infrastructures
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
prev parent reply other threads:[~2019-12-20 10:25 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-24 15:02 Bioconductor package flowPeaks license Artistic 1.0? zimoun
2019-07-24 21:15 ` Ricardo Wurmus
2019-07-25 9:58 ` zimoun
2019-07-25 12:47 ` Ricardo Wurmus
2019-12-19 16:38 ` zimoun
2019-12-19 17:17 ` Ricardo Wurmus
2019-12-19 17:29 ` zimoun
2019-12-19 20:10 ` Ricardo Wurmus
2019-12-19 21:18 ` zimoun
2019-12-19 17:18 ` Tobias Geerinckx-Rice
2019-12-19 17:29 ` Tobias Geerinckx-Rice
2019-12-19 18:04 ` zimoun
2019-12-19 17:56 ` zimoun
2019-12-19 20:24 ` Tobias Geerinckx-Rice
2019-12-19 21:40 ` zimoun
2019-12-20 9:28 ` Giovanni Biscuolo
2019-12-20 10:47 ` zimoun
2019-12-20 14:40 ` Ricardo Wurmus
2019-12-20 11:55 ` Guix and Bioconductor Giovanni Biscuolo
2019-12-20 14:38 ` Ricardo Wurmus
2019-12-21 10:06 ` [OT] " Giovanni Biscuolo
2019-12-19 18:18 ` Bioconductor package flowPeaks license Artistic 1.0? zimoun
2019-12-20 10:24 ` Giovanni Biscuolo [this message]
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=87k16r70re.fsf@roquette.mug.biscuolo.net \
--to=g@xelera.eu \
--cc=guix-devel@gnu.org \
--cc=me@tobias.gr \
--cc=zimon.toutoune@gmail.com \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.