From: zimoun <zimon.toutoune@gmail.com>
To: "Simon Josefsson" <simon@josefsson.org>,
"Ludovic Courtès" <ludo@gnu.org>
Cc: Vagrant Cascadian <vagrant@debian.org>, guix-devel@gnu.org
Subject: Re: advanced?
Date: Mon, 28 Nov 2022 19:36:03 +0100 [thread overview]
Message-ID: <86a64bq63w.fsf@gmail.com> (raw)
In-Reply-To: <871qpnp28t.fsf@latte>
Hi,
On Mon, 28 Nov 2022 at 15:44, Simon Josefsson via "Development of GNU Guix and the GNU System distribution." <guix-devel@gnu.org> wrote:
> Yes, that makes sense. I'm not the best person to summarize it, but
> starting pointers if someone wants to take it further:
Well, it is somehow part of,
* Transactional upgrades and roll-backs
* Reproducible build environments
I would also add Inferiors and Time-machine, especially working in
tandem with Software Heritage. AFAIU, it is unique to be able to jump
to (almost) any point back in time and just rebuild (or almost), with
one command-line, whatever the state of the world (or almost). It
pushes far beyond features such as https://snapshot.debian.org/ IMHO.
Cheers,
simon
next prev parent reply other threads:[~2022-11-28 18:41 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-26 21:47 advanced? Simon Josefsson via Development of GNU Guix and the GNU System distribution.
2022-11-27 8:51 ` advanced? Liliana Marie Prikler
2022-11-27 12:39 ` advanced? zimoun
2022-11-27 17:22 ` advanced? Ryan Prior
2022-11-27 18:35 ` advanced? Vagrant Cascadian
2022-11-28 11:18 ` advanced? Ludovic Courtès
2022-11-28 14:44 ` advanced? Simon Josefsson via Development of GNU Guix and the GNU System distribution.
2022-11-28 18:36 ` zimoun [this message]
2023-01-04 11:00 ` advanced? Ludovic Courtès
2023-01-09 12:02 ` advanced? Simon Josefsson via Development of GNU Guix and the GNU System distribution.
2022-11-28 15:35 ` advanced? Denis 'GNUtoo' Carikli
2023-01-04 10:54 ` advanced? Ludovic Courtès
2023-01-09 11:12 ` advanced? Ludovic Courtès
2023-01-09 11:37 ` advanced? Julien Lepiller
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=86a64bq63w.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.org \
--cc=simon@josefsson.org \
--cc=vagrant@debian.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.