all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Pjotr Prins <pjotr.public12@thebird.nl>
To: Dave Love <fx@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: Hacks to install Guix packages without root
Date: Mon, 6 Nov 2017 17:13:03 +0100	[thread overview]
Message-ID: <20171106161303.GA26300@thebird.nl> (raw)
In-Reply-To: <87shdrwit9.fsf@albion.it.manchester.ac.uk>

On Mon, Nov 06, 2017 at 03:03:30PM +0000, Dave Love wrote:
> > Best to try for the specific use case. For bioinformatics it won't
> > work.
> 
> This may be a bit off-topic, but perhaps it helps in packaging:  I don't
> know whether that refers to using PRoot or fakechroot, but anyway,
> what specifically is the problem in bioinformatics?

Large data sets. Many files.

> By the way, I measured compressed tar/untar under PRoot on CentOS 6 of
> the CentOS root image.  It's around a factor of two slower than native
> on untar and about 40% slower on tar.

Exactly. Too slow when IO is already the bottleneck.

> > Docker is not going away, mind. We may end up putting Conda and Guix
> > in Docker containers ;)
> 
> Does that mean containers or images?  (The way the terminology has gone
> is rather unhelpful...)  

Containers.

> Docker is a nightmare for use with HPC-type
> resource managers, but you can run from OCI-type images more sanely, of
> course.

There is no love between Docker and me ;)

> I probably basically agree!

Probably :)


-- 

  reply	other threads:[~2017-11-06 16:15 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-26 21:46 Hacks to install Guix packages without root Ricardo Wurmus
2017-10-27  0:48 ` Ludovic Courtès
2017-10-27  8:27   ` Pjotr Prins
2017-10-31 14:19     ` Dave Love
2017-11-03 11:54       ` Pjotr Prins
2017-11-06 15:03         ` Dave Love
2017-11-06 16:13           ` Pjotr Prins [this message]
2017-10-27  6:53 ` Konrad Hinsen
2017-10-27  8:17 ` Pjotr Prins

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=20171106161303.GA26300@thebird.nl \
    --to=pjotr.public12@thebird.nl \
    --cc=fx@gnu.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 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.