From mboxrd@z Thu Jan  1 00:00:00 1970
From: Andreas Enge <andreas@enge.fr>
Subject: Re: Tip of the day: storing your GuixSD config in the instantiated
	system
Date: Tue, 29 Aug 2017 12:30:19 +0200
Message-ID: <20170829103019.GA1516@jurong>
References: <871snzfl4s.fsf@gnu.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Return-path: <help-guix-bounces+gcggh-help-guix=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:4830:134:3::10]:39450)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <andreas@enge.fr>) id 1dmdmu-0005ZD-BW
	for help-guix@gnu.org; Tue, 29 Aug 2017 06:30:29 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <andreas@enge.fr>) id 1dmdmq-00043B-DD
	for help-guix@gnu.org; Tue, 29 Aug 2017 06:30:28 -0400
Received: from mailrelay1-2.pub.mailoutpod1-cph3.one.com ([46.30.212.0]:21374)
	by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32)
	(Exim 4.71) (envelope-from <andreas@enge.fr>) id 1dmdmq-00041u-43
	for help-guix@gnu.org; Tue, 29 Aug 2017 06:30:24 -0400
Content-Disposition: inline
In-Reply-To: <871snzfl4s.fsf@gnu.org>
List-Id: <help-guix.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/help-guix>,
	<mailto:help-guix-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/help-guix/>
List-Post: <mailto:help-guix@gnu.org>
List-Help: <mailto:help-guix-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/help-guix>,
	<mailto:help-guix-request@gnu.org?subject=subscribe>
Errors-To: help-guix-bounces+gcggh-help-guix=m.gmane.org@gnu.org
Sender: "Help-Guix" <help-guix-bounces+gcggh-help-guix=m.gmane.org@gnu.org>
To: Ludovic =?iso-8859-15?Q?Court=E8s?= <ludo@gnu.org>
Cc: help-guix <help-guix@gnu.org>

On Fri, Aug 25, 2017 at 10:27:47PM +0200, Ludovic Courtès wrote:
> But wait: we can already store the config file in the instantiated
> system!  Here’s how:

That is an exciting trick, thank you, Ludovic!

As for making it a "default", this could be done in two ways:
- Add it as a service to %base-services.
- Add it to the configuration templates.
I am more in favour of the first option, as it puts less clutter into
the configuration file.

As Ricardo, I do not think we should leave out the argument to
"guix system reconfigure" - this is too much automation in my opinion,
it is good if users explicitly provide their desired configuration.
And if it is only a matter of adding "/etc/config.scm" to express that
nothing has changed and that just an update of the same packages and
services is to be done, then this can be done easily now.

Andreas