unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Cook, Malcolm" <MEC@stowers.org>
To: 'Guix-devel' <guix-devel@gnu.org>,
	"'bio-packaging@mailman.open-bio.org'"
	<bio-packaging@mailman.open-bio.org>
Subject: Making the case for GNU Guix ... advice sought
Date: Mon, 8 Feb 2016 19:43:25 +0000	[thread overview]
Message-ID: <953f16876af34ea59b526b7f35482e72@exchsrv2.sgc.loc> (raw)

Hi,

I have been asked to write up an argument for the advantages that GNU Guix confers for deploying linux software, especially scientific computing and including bioinformatics software.
	
To that end I have written up this document 

	https://github.com/malcook/sce/blob/master/MakingTheCase.org

and I welcome all criticism, suggestions, observations, omissions, flames, what-have-you.    Please feel free to discuss in this thread, via private email, pull requests, as you see fit.   

I hope to incorporate the "good parts" of this discussion back into the document and welcome anyone to use as they see fit (that would be a nice outcome!).

I have some notes contrasting GNU Guix with other similar/related tool-sets (modules, lmod, homebrew, spack, easyBuild, rolling rpms), as well as our current practices (sort of hybrid of rpms, bastard son of homebrew, and "just wedge it in there").  However I am not now intent upon setting up such a contrast, rather, I hope to focus on the advantages of GNU Guix in general.

Some of my comments may be naïve/mis-informed as my experience with guix so far has been small personal testing deployments, and I have not worked out all the details of deploying " Using a shared Guix store" as discussed here: http://guix-devel.gnu.narkive.com/tk2nRunF/using-a-shared-guix-store-was-re-bio-packaging-testing-out-guix - about which I also welcome further comments, suggestions, and/or warnings.

Thanks,

Malcolm Cook
 

             reply	other threads:[~2016-02-08 19:43 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-08 19:43 Cook, Malcolm [this message]
2016-02-09 15:03 ` Making the case for GNU Guix ... advice sought 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
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

  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=953f16876af34ea59b526b7f35482e72@exchsrv2.sgc.loc \
    --to=mec@stowers.org \
    --cc=bio-packaging@mailman.open-bio.org \
    --cc=guix-devel@gnu.org \
    /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).