From: Ricardo Wurmus <rekado@elephly.net>
To: zimon.toutoune@gmail.com
Cc: guix-devel@gnu.org
Subject: Re: Bioconductor package flowPeaks license Artistic 1.0?
Date: Wed, 24 Jul 2019 23:15:55 +0200 [thread overview]
Message-ID: <87pnlz9lro.fsf@elephly.net> (raw)
In-Reply-To: <CAJ3okZ0fgUr3j7D1ECX=Xsc+qbcxW_MMuia5TmQs8MTjKnBN0Q@mail.gmail.com>
zimoun <zimon.toutoune@gmail.com> writes:
> I am packaging bunch of Flow Cytometry packages and `flowPeaks` says
> Artistic 1.0 license.
> See https://www.bioconductor.org/packages/release/bioc/manuals/flowPeaks/man/flowPeaks.pdf
>
> And in `license.scm` there is only the 2.0.
That’s because version 1.0 is considered non-free. “licenses.scm” also
contains “clarified-artistic”, which is essentially the same as version
1.0 but with a few clarifications of those points that could be
interpreted as conditions making the software non-free.
--
Ricardo
next prev parent reply other threads:[~2019-07-24 21:16 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 [this message]
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 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87pnlz9lro.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=guix-devel@gnu.org \
--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.