From: Leo Famulari <leo@famulari.name>
To: Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de>
Cc: guix-devel@gnu.org,
"'bio-packaging@mailman.open-bio.org'"
<bio-packaging@mailman.open-bio.org>
Subject: Re: Making the case for GNU Guix ... advice sought
Date: Tue, 9 Feb 2016 14:54:37 -0500 [thread overview]
Message-ID: <20160209195437.GB6122@jasmine> (raw)
In-Reply-To: <idjmvra6i4u.fsf@bimsb-sys02.mdc-berlin.net>
On Tue, Feb 09, 2016 at 04:03:13PM +0100, Ricardo Wurmus wrote:
>
> Cook, Malcolm <MEC@stowers.org> writes:
> > + Guix development is open source. It is open to input from all
> > community members.
>
> It’s free software ;)
>
> Maybe it’s also good to mention that you do not need to rely on Guix
> upstream to add packages. It is trivial to use custom packages with
> GUIX_PACKAGE_PATH.
It can't be overstated *how* trivial it is. I've found that users of
mutable-state package managers just don't believe me when I tell them.
It's even easy to have out-of-tree packages, pulled in with
GUIX_PACKAGE_PATH, that depend on in-tree packages or package updates
that you haven't upstreamed yet.
next prev parent reply other threads:[~2016-02-09 19:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-08 19:43 Making the case for GNU Guix ... advice sought Cook, Malcolm
2016-02-09 15:03 ` Ricardo Wurmus
2016-02-09 19:54 ` Leo Famulari [this message]
2016-02-09 20:27 ` Ludovic Courtès
2016-02-09 20:30 ` Ludovic Courtès
2016-02-18 23:29 ` Cook, Malcolm
2016-02-19 10:10 ` Pjotr Prins
2016-02-19 15:06 ` Cook, Malcolm
2016-02-28 13:52 ` Ludovic Courtès
2016-02-28 14:42 ` Ricardo Wurmus
2016-02-29 16:55 ` Cook, Malcolm
2016-02-29 17:10 ` Cook, Malcolm
2016-03-01 21:22 ` Ludovic Courtès
2016-02-09 20:36 ` Ludovic Courtès
2016-02-10 16:01 ` Cook, Malcolm
2016-02-18 23:26 ` Cook, Malcolm
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=20160209195437.GB6122@jasmine \
--to=leo@famulari.name \
--cc=bio-packaging@mailman.open-bio.org \
--cc=guix-devel@gnu.org \
--cc=ricardo.wurmus@mdc-berlin.de \
/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.