all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Andy Wingo <wingo@igalia.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Introducing ‘guix pack’
Date: Mon, 13 Mar 2017 11:18:14 +0100	[thread overview]
Message-ID: <87k27tv5sp.fsf@igalia.com> (raw)
In-Reply-To: <87d1dodcnb.fsf@gnu.org> ("Ludovic Courtès"'s message of "Fri, 10 Mar 2017 22:50:48 +0100")

On Fri 10 Mar 2017 22:50, ludo@gnu.org (Ludovic Courtès) writes:

> I had it on my to-do list and Andy said he’d like to have something like
> that to publish Guile 2.2 binaries: the ‘guix pack’ command below is a
> generalization of the code that builds the Guix binary tarball¹.  It
> creates a bundle of the closure of the given packages, with a profile
> containing all the packages.

Very cool, thank you!!!

> Andy, does this correspond to what you have in mind?

Yes, though I hadn't thought everything out.  I guess my mail question
is about user experience -- this is going to be a gateway for people to
get Guix and Guile and we should make sure there are no rough edges.  I
guess in particular I have a concern about users overwriting their
/var/guix.  (No worries about overwriting /gnu/store of course.)

Particularly if a user installs one "guix pack" then installs another
"guix pack", what happens?  Does the /var/guix tarball include the
sqlite db?  Could it be overwritten?  What if the user had already
installed Guix already; does this silently trash their Guix install?

A bug report: I just tried it but it seems guix pack doesn't respect
--no-build-hook for some reason, and also for some reason on this
machine my Guix daemon fails with "offload: command not found", which I
was getting around via --no-build-hook.

I guess what would be ideal would be:

  cd /
  sudo tar xvf aasdfafasdfjasdaldfhasdfh-guile.tar.xz

and then telling the user to run via
/gnu/store/asasdfadfgsadfa-profile/bin/guile.  That way there is very
little risk of trashing the user's system.

Of course we could also provide them a README of sorts for all the load
paths, but in the end this is a gateway to the real experience :)

I guess for binary installs you would of course want /var/guix, the
database, and the profiles.  I think in that case it makes sense to add
an option to --pack about including them, and have it default to off
(given the potential to trample a user's store).

WDYT?  Any of this make sense? :)

Andy

  parent reply	other threads:[~2017-03-13 10:19 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-10 21:50 Introducing ‘guix pack’ Ludovic Courtès
2017-03-10 23:43 ` Ricardo Wurmus
2017-03-11 21:05 ` Chris Marusich
2017-03-12 16:56   ` Ludovic Courtès
2017-03-12 23:03     ` Ricardo Wurmus
2017-03-13  7:44     ` Chris Marusich
2017-03-13 10:18 ` Andy Wingo [this message]
2017-03-14 13:42   ` Ludovic Courtès
2017-03-14 14:00     ` Andy Wingo
2017-03-14 17:02       ` Ludovic Courtès
2017-03-19 17:13         ` Federico Beffa
2017-03-19 22:56           ` Ludovic Courtès
2017-03-20  8:09             ` Federico Beffa
2017-03-20 14:14               ` Ludovic Courtès
2017-03-21 10:48                 ` Andy Wingo
2017-03-22  8:48                   ` Federico Beffa
2017-03-24  9:56                     ` Ludovic Courtès
2017-03-20 14:16               ` Ludovic Courtès
2017-03-20 15:16                 ` Alex Sassmannshausen
2017-03-16 22:28 ` Ludovic Courtès
2017-03-17 17:23   ` Pjotr Prins
2017-03-17 23:43     ` Ludovic Courtès
2017-03-17 23:49   ` Ludovic Courtès
2017-03-19 12:01     ` Jan Nieuwenhuizen
2017-03-20 14:20   ` Clément Lassieur
2017-03-20 15:14     ` Ricardo Wurmus
2017-03-20 15:41       ` Ludovic Courtès

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=87k27tv5sp.fsf@igalia.com \
    --to=wingo@igalia.com \
    --cc=guix-devel@gnu.org \
    --cc=ludo@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.