From: Andy Wingo <wingo@igalia.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel <guix-devel@gnu.org>, Federico Beffa <beffa@ieee.org>
Subject: Re: Introducing ‘guix pack’
Date: Tue, 21 Mar 2017 11:48:53 +0100 [thread overview]
Message-ID: <cucbmsuq50q.fsf@igalia.com> (raw)
In-Reply-To: <87fui8m3vz.fsf@gnu.org> ("Ludovic Courtès"'s message of "Mon, 20 Mar 2017 15:14:40 +0100")
On Mon 20 Mar 2017 15:14, ludo@gnu.org (Ludovic Courtès) writes:
> Federico Beffa <beffa@ieee.org> skribis:
>
>> If you provide an archive such as
>> 'guile-2.2.0-pack-x86_64-linux-gnu.tar.lz' reachable from the main
>> project page (especially without any warning about its intended
>> purpose), I bet that many peoples will install it and keep it. If more
>> projects follow this example, we land to the above scenario where "rm
>> -rf /gnu" is not practical at all.
Replying to Federico: These are the same considerations as with Guix
fwiw, unless you remove old profiles and "guix gc".
Another solution to this concern is to remove /gnu/store and re-unpack
the tarballs that you still want.
Generally though I think we shouldn't expect people to access the store
directly; they'd only use /opt/gnu or whatever. In the case that you
have upgraded the software, surely the problem is fixed (though of
course you may fix the problem for pack A but not pack B).
The natural solution is to use a package manager of course, as you note
:)
> I agree, there’s always a risk. I think what we can do is communicate
> about these risks, and avoid using distributing packs in situations that
> make it too likely that people will keep the pack without ever
> upgrading.
Agreed, though I wouldn't over-stress the risks to be honest -- Guix
gives both users and distributors the ability to generate a new pack
easily. A user can decide not to upgrade even in a system that is
managed by Guix. User freedom is all of this :)
Andy
next prev parent reply other threads:[~2017-03-21 10:49 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 [this message]
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
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=cucbmsuq50q.fsf@igalia.com \
--to=wingo@igalia.com \
--cc=beffa@ieee.org \
--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 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).