From: ludo@gnu.org (Ludovic Courtès)
To: Federico Beffa <beffa@ieee.org>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Introducing ‘guix pack’
Date: Fri, 24 Mar 2017 10:56:03 +0100 [thread overview]
Message-ID: <87tw6jxaks.fsf@gnu.org> (raw)
In-Reply-To: <87zigdofxq.fsf@lupo.i-did-not-set--mail-host-address--so-tickle-me> (Federico Beffa's message of "Wed, 22 Mar 2017 09:48:17 +0100")
Hi,
Federico Beffa <beffa@ieee.org> skribis:
> Suppose that Guix pack bundles become popular and compare them to,
> say, Mac style archives. Let's go through Ludovic's analysis:
>
> 1. Composability: With Mac bundles you extract the archive in a
> directory. With Guix packs it's essentially the same.
>
> i. Sharing of store items: What are the chances that two
> independent projects will generate packs from the same git checkout
> (or guix pull)? Pretty low. Therefore the amount of sharing
> between different packs will be pretty negligible.
That’s not true; you’d be likely to share glibc, gcc:lib, maybe GLib,
GTK+, etc.
> ii. Adding a program. Mac style: you just extract it. With Guix
> pack it's essentially the same, but it creates a manually
> unmanageable network of links which entangle all packs.
>
> iii. Remove an item: Mac style: delete a directory. With Guix pack
> the choice is: delete everything or keep everything. That is, you
> keep obsolete programs/libraries with security holes on your system
> ready for exploitation and unnecessarily filling your disk, or
> ... start from scratch. Is this composability?
>
> 2. Security: Mac style bundles are problematic, but at least you can
> easily delete old stuff and replace them with updated versions.
> Guix packs are worse: delete everything or keep it all.
>
> 3. Reproducibility: As long as you carefully take note from which git
> checkout you generate a Guix pack, Guix packs seems to be superior.
> Oh, don't you also depend on upsteam published archives of every
> single package in Guix? They sometimes disappear or are replaced
> in place with different archives and so, after some time, your
> carefully noted git checkout will not build anymore.
>
> 4. Experimentation: Guix is great for that, but packs? Are they
> useful for testing on other GNU/Linux systems? Maybe. But aren't
> all Guix packages built in isolated environments anyway? So, do
> you really need packs to test on other systems? Maybe, but
> probably not.
>
> Don't get me wrong, I find that Guix proper has many great features,
> but pack is not one of them.
Don’t get me wrong, I agree! :-)
Again, I think packs are useful in some cases where the other options
are even worse, but I’m not advocating it as a general “solution.”
In the news entry online I tried to take into account the very
legitimate criticisms you made, but perhaps the end result didn’t make
it sufficiently clear that packs aren’t a general solution.
Ludo’.
next prev parent reply other threads:[~2017-03-24 9:56 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
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 [this message]
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
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=87tw6jxaks.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=beffa@ieee.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).