From: Ricardo Wurmus <rekado@elephly.net>
To: zimoun <zimon.toutoune@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: Bioconductor package flowPeaks license Artistic 1.0?
Date: Fri, 20 Dec 2019 15:40:28 +0100 [thread overview]
Message-ID: <874kxvqcv7.fsf@elephly.net> (raw)
In-Reply-To: <CAJ3okZ00MhGfunGJzr2srW0qRc2yqWjoXj6v5dqKNkRbwjWP6w@mail.gmail.com>
zimoun <zimon.toutoune@gmail.com> writes:
> This fix -- reuse all the free available code and replace the non-free
> one -- do not scale.
> So the question is: What is the scale we are talking about? How many
> packages in Bioconductor?
> If it is, say, a couple then it is doable. Or see with the people
> managing Bioconductor.
> If it is more, then the option is lobbying. :-)
In my experience tt happens rarely enough that it appears to scale just
fine. Every time it happens is a drag, of course, but only a small
percentage of CRAN and Bioconductor packages suffers from problems like
that. That’s still an estimated dozens of packages, but it’s not quite
as bad as it may seem.
--
Ricardo
next prev parent reply other threads:[~2019-12-20 14:40 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 [this message]
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=874kxvqcv7.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.