unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: zerodaysfordays@sdf.lonestar.org (Jakob L. Kreuze)
To: Mark H Weaver <mhw@netris.org>
Cc: guix-devel@gnu.org, 36855@debbugs.gnu.org
Subject: bug#36855: guix system switch-generation doesn't
Date: Wed, 28 Aug 2019 20:08:19 -0400	[thread overview]
Message-ID: <87k1awomto.fsf@sdf.lonestar.org> (raw)
In-Reply-To: <875zmhm8jo.fsf@netris.org> (Mark H. Weaver's message of "Wed, 28 Aug 2019 14:46:56 -0400")

[-- Attachment #1: Type: text/plain, Size: 1008 bytes --]

Hi Mark,

Mark H Weaver <mhw@netris.org> writes:

> Hi Jakob,
>
> zerodaysfordays@sdf.lonestar.org (Jakob L. Kreuze) writes:
>
>> Thanks for the input; I wasn't aware that the activation process was
>> taking so long for some people. One of Ludovic's suggestions was to
>> create a single derivation, rather than three, to speed up system
>> activation. I'll look into this further.
>
> To be clear, I don't care how long it takes to build these
> derivations. However, I think they should all be built before starting
> to activate the system. Does that make sense?

Yes, and I agree that it would be ideal to have the derivations built
prior to system activation -- that way, the activation scripts could be
included in 'show-what-to-build*'.

> On a side note, what would happen if one of those builds failed? Would
> the system activation be left half-done?

Yes. You raise another very good reason for why system activation should
be carried out by a single, atomic activation script :)

Regards,
Jakob

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

  parent reply	other threads:[~2019-08-29  0:09 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-30 10:00 bug#36855: guix system switch-generation doesn't Robert Vollmert
2019-07-30 16:16 ` Jakob L. Kreuze
2019-08-06 21:21 ` Robert Vollmert
2019-08-06 21:25 ` Robert Vollmert
     [not found] ` <A3C3B87A-1B74-4983-A8EA-7281E3103567@vllmrt.net>
2019-08-07 19:37   ` Christopher Lemmer Webber
2019-08-07 19:57     ` Jakob L. Kreuze
     [not found]     ` <877e7on3zd.fsf@sdf.lonestar.org>
2019-08-08 16:40       ` Chris Marusich
     [not found]       ` <87h86ry5j5.fsf@gmail.com>
2019-08-08 17:03         ` Robert Vollmert
     [not found]         ` <51A8B412-1AE3-4464-8146-DE8B19B7C4DF@vllmrt.net>
2019-08-09  7:35           ` Chris Marusich
2019-08-26 10:07         ` Ludovic Courtès
2019-08-26 18:51           ` Mark H Weaver
2019-08-28  0:34             ` Mark H Weaver
2019-08-28 18:33               ` Jakob L. Kreuze
2019-08-28 18:46                 ` Mark H Weaver
     [not found]                 ` <875zmhm8jo.fsf@netris.org>
2019-08-29  0:08                   ` Jakob L. Kreuze [this message]
     [not found]         ` <874l241bq6.fsf@gnu.org>
2019-08-28 18:28           ` Jakob L. Kreuze
2021-03-09  7:01 ` bug#36855: bug#37596: 'guix system switch-generation' does not reload Shepherd services Brice Waegeneire

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=87k1awomto.fsf@sdf.lonestar.org \
    --to=zerodaysfordays@sdf.lonestar.org \
    --cc=36855@debbugs.gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=mhw@netris.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).