From: Andreas Enge <andreas@enge.fr>
To: Jone <yeger9@gmail.com>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: Modify system behavior after reconfigure
Date: Sat, 17 Mar 2018 12:54:40 +0100 [thread overview]
Message-ID: <20180317115440.GA2527@jurong> (raw)
In-Reply-To: <20180317160635.3c3949d8@gmail.com>
On Sat, Mar 17, 2018 at 04:06:35PM +0300, Jone wrote:
> Ricardo writes:
> > Reconfiguring does not take a lot of time when there have been only
> > minor changes. It only takes a couple of seconds.
> Well, let's just say, this is not always true. The last time was a full
> compilation of Icecat from source (!) "It only takes a couple of
> hours" ;)
Ricardo is right if you do not make other, *unrelated* changes - of course
updating icecat may trigger a rebuild of icecat.
So in the case of only changing some configuration items, one would need
to make sure to use the exact same copy of guix as for the previous
configuration. Either one should not do a "guix pull" in between, or one
can keep a git checkout on the same branch or commit and do a
"./pre-inst-env guix system reconfigure...".
Then updating everything can be done at a separate occasion (over night,
for instance, or after icecat has been built on the substitute server).
Also, this problem can be circumvented by not having packages in the *system*
definition, but only in *user* profiles. This decouples updates of single
packages from updates of the system configuration.
Andreas
next prev parent reply other threads:[~2018-03-17 11:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-17 12:18 Modify system behavior after reconfigure Jone
2018-03-17 9:30 ` Ricardo Wurmus
2018-03-17 13:06 ` Jone
2018-03-17 11:25 ` Ricardo Wurmus
2018-03-17 14:50 ` Jone
2018-03-19 3:47 ` Chris Marusich
2018-03-17 11:54 ` Andreas Enge [this message]
2018-03-17 15:20 ` Jone
2018-03-20 10:58 ` Ludovic Courtès
2018-03-20 20:12 ` Jone
2018-03-20 18:23 ` Oleg Pykhalov
2018-03-20 19:56 ` Alex Kost
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=20180317115440.GA2527@jurong \
--to=andreas@enge.fr \
--cc=help-guix@gnu.org \
--cc=yeger9@gmail.com \
/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.
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).