From: zimoun <zimon.toutoune@gmail.com>
To: Tobias Geerinckx-Rice <me@tobias.gr>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: Bioconductor package flowPeaks license Artistic 1.0?
Date: Thu, 19 Dec 2019 19:18:55 +0100 [thread overview]
Message-ID: <CAJ3okZ1jgxEKHabDYW8wC5jEqUd3vpyQ6jnMmtGtXVd6OUwTXA@mail.gmail.com> (raw)
In-Reply-To: <87k16si685.fsf@nckx>
Hi Tobias, again :-)
On Thu, 19 Dec 2019 at 18:18, Tobias Geerinckx-Rice <me@tobias.gr> wrote:
> zimoun 写道：
> > Especially when this
> > very Artistic 1.0 "qualifies as a free software license, but it
> > may
> > not be a real copyleft" [1].
>
> …but that's not this very licence, it's a completely different
> one: the (disjunct) combination of the Artistic 1.0 licence *and
> the GPL*, i.e. ‘choose one’. The result is only free because you
> can *ignore* the Artistic 1.0 part.
Maybe I misread. And I would like to avoid any confusion.
So I have also read the French translation. Then again the English version.
Where is the License of Perl 5 and below explicitly defined? There is
no pointer...
What I understand is: when the License of Perl 5 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.
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. 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 and because it is not Guix related, I would like to
ask to GNU or FSF. Do you know where can I post an email?
All the best,
simon
next prev parent reply other threads:[~2019-12-19 18:19 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 ` zimoun [this message]
2019-12-20 10:24 ` Perl modules dual licensing (was Re: Bioconductor package flowPeaks license Artistic 1.0?) Giovanni Biscuolo
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAJ3okZ1jgxEKHabDYW8wC5jEqUd3vpyQ6jnMmtGtXVd6OUwTXA@mail.gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=guix-devel@gnu.org \
--cc=me@tobias.gr \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).