all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Cook, Malcolm" <MEC@stowers.org>
To: 'Pjotr Prins' <pjotr.public66@thebird.nl>
Cc: "guix-devel@gnu.org" <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: Fri, 19 Feb 2016 15:06:59 +0000	[thread overview]
Message-ID: <c8a07212463947c3831cea0bdd0af827@exchsrv2.sgc.loc> (raw)
In-Reply-To: <20160219101029.GA14210@thebird.nl>

Pjotr!

> > Yes.  Agreed.  However, my emphasis here was intended to be that
 > > Guix can be used to obviate the need for rbenv, virtualenv, and
 > > friends.    I thought that `guix environment` was going to be an
 > > effective replacement for them.  Am I mistaken in this?
 > 
 > I have dropped rbenv, virtualenv and even bundler from my working
 > environments, thanks to Guix! I am really, really, really happy
 > about that.
 > 
 > I even have different profiles for different ruby versions (one is on
 > 1.8.7).

Glad to hear to the positive news.  Looking forward to this too.

> > I hope
 > > not!  Assuming not, and if I understand your point, then I should
 > > write instead that this by virtue of guix's ability to set-up and
 > > tear down environments/profiles that not only specify versions of
 > > applications, but also libraries/plug-ins/modules for a variety of
 > > languages (ruby, perl, etc) and tools (emacs, etc).  You mention the
 > > importance of 'importers' below... perhaps it is the combination of
 > > available importers (for scaffolding the packaging from external
 > > repos) along with the ability to use `guix environment` to make them
 > > available in specified contexts.
 > 
 > Yes, you need to create packages for all gems and Python modules in
 > use. Importers help define packages quickly.

Again, thanks for confirmation, and for your succinct paraphrasing of this consideration.

~Malcolm

 > 
 > Pj.

  reply	other threads:[~2016-02-19 15:07 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
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 [this message]
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=c8a07212463947c3831cea0bdd0af827@exchsrv2.sgc.loc \
    --to=mec@stowers.org \
    --cc=bio-packaging@mailman.open-bio.org \
    --cc=guix-devel@gnu.org \
    --cc=pjotr.public66@thebird.nl \
    /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.