unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: sirgazil <sirgazil@zoho.com>
To: Tobias Geerinckx-Rice <me@tobias.gr>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: guix system reconfigure /etc/config.scm or my-config.scm
Date: Wed, 08 May 2019 19:50:30 -0500	[thread overview]
Message-ID: <16a9a11f9a3.b3685ee490782.1286119268062071099@zoho.com> (raw)
In-Reply-To: <87woj0g3g6.fsf@nckx>

---- On Wed, 08 May 2019 14:18:33 -0500 Tobias Geerinckx-Rice <me@tobias.gr> wrote ----

 > Hiya Sirgazil, 
 >  
 > sirgazil wrote: 
 > > So, should one do the following instead? 
 > > 
 > >     $ emacs ~/path/to/my-config.scm 
 > >     Modify the file to your liking 
 > >     $ guix pull && sudo guix system reconfigure 
 > >     ~/path/to/my-config.scm 
 >  
 > Oh, it doesn't matter. 
 >  
 > This file can be whatever and wherever you want it to be (mine's 
 > /etc/guix/system.scm because eww ‘config’).  It's in /etc by 
 > default since that's where most people will expect it and it's the 
 > Unixly-correct place to put system-wide configuration files, and 
 > this is the mother of all system-wide configuration files :-) 
 >  
 > Now, to be blunt, I don't think 
 >  
 >  “The normal way to change the system configuration is by 
 >  updating this 
 >  file and re-running ‘guix system reconfigure’.  One should 
 >  never have 
 >  to touch files in ‘/etc’[.]” 
 >  
 > can reasonably be read as self-contradictory, but if you want to 
 > add an ‘other’ at the end I don't think anyone will object! 

Thanks for your help, Tobias :)

      reply	other threads:[~2019-05-09  0:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-08 18:54 guix system reconfigure /etc/config.scm or my-config.scm sirgazil
2019-05-08 19:16 ` John Soo
2019-05-09  0:46   ` sirgazil
2019-05-08 19:18 ` Tobias Geerinckx-Rice
2019-05-09  0:50   ` sirgazil [this message]

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=16a9a11f9a3.b3685ee490782.1286119268062071099@zoho.com \
    --to=sirgazil@zoho.com \
    --cc=help-guix@gnu.org \
    --cc=me@tobias.gr \
    /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).