all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Tobias Geerinckx-Rice <me@tobias.gr>
To: Chris Marusich <cmmarusich@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: Seeking guidance regarding system roll-back and switch-generation
Date: Sun, 17 Jul 2016 17:27:15 +0200	[thread overview]
Message-ID: <93df5c106c7e10c24687ee355b972f72@tobias.gr> (raw)
In-Reply-To: <87twfo7h5v.fsf@gmail.com>

Ahoy Chris,

Just one aside, for context:

(And to softly nudge people into the right™ direction of activation
scripts, of course. ;-)

On 2016-07-17 11:22, Chris Marusich wrote:
> However, it may not be necessary to generate a 
> "switch-to-configuration"
> script at all.  Instead, what if we just stored the operating system
> configuration file in a well known location within each system
> generation?

NixOS offers this option. I've forgot the name, because its utility is
so limited, and its main use is to confuse people on IRC.

All it does is copy /etc/nixos/configuration.nix to the store. That's
it. All your imports are now broken, if they pointed to a relative path
that doesn't exist in the store, or impure, if they pointed to an 
absolute
path that wasn't immutable. This breaks all but the most trivial (or
unmaintainable) set-ups. Even the NixOS installer creates a multi-file
configuration by default.

That no-one has bothered to script a solution probably means something.

Kind regards,

T G-R

  reply	other threads:[~2016-07-17 15:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-17  9:22 Seeking guidance regarding system roll-back and switch-generation Chris Marusich
2016-07-17 15:27 ` Tobias Geerinckx-Rice [this message]
2016-07-18 12:39   ` Ludovic Courtès
2016-07-18 13:01 ` Ludovic Courtès
2016-07-19  8:35   ` Chris Marusich
2016-07-22 10:32     ` Chris Marusich
2016-07-22 15:49     ` Ludovic Courtès
2016-07-25  6:22       ` Chris Marusich
2016-07-25  8:06         ` 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=93df5c106c7e10c24687ee355b972f72@tobias.gr \
    --to=me@tobias.gr \
    --cc=cmmarusich@gmail.com \
    --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.