From: Catonano <catonano@gmail.com>
To: Tobias Geerinckx-Rice <me@tobias.gr>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: conf file - where is it ?
Date: Sat, 9 May 2020 19:52:17 +0200 [thread overview]
Message-ID: <CAJ98PDzHMcgqxwWR9_Hik-LhaXJYt8ptuKXf7uLb2tE0a3UYXQ@mail.gmail.com> (raw)
In-Reply-To: <87imh5owsk.fsf@nckx>
Il giorno sab 9 mag 2020 alle ore 19:14 Tobias Geerinckx-Rice <me@tobias.gr>
ha scritto:
> Catonano,
>
> Catonano 写道:
> > ehm... and how will I know when it's been updated ?
>
> The release manager (i.e. Ludo') sends a message to the list when
> there's a new release, and it's generally a big deal. A minor
> bugfix release would be no different.
>
> However, there's no reason to download binary snapshots from
> gnu.org if you have Guix installed. In fact I'd recommend against
> it.
>
> Any reason you can't guix pull && build it yourself?
>
>
I haven't Guix installed.
I'm running Ubuntu and I'm a bit wary of installing Guix on top of it
because I remember the obsessive reporting by apparmor about Guix
attempting to do something
Also, I don't want the package manager, I want the whole distro
That's why I chose to run the image for Qemu, so I could have the whole
thing but without managing (too much) operating systems, which I despise
My idea was that I would have used the configuration file as a starting
point for reconfiguring the machine running in Qemu
But it's not a big deal, I'll wait
Thank you Tobias !
next prev parent reply other threads:[~2020-05-09 17:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-03 18:41 conf file - where is it ? Catonano
2020-05-03 18:55 ` Vincent Legoll
2020-05-03 19:54 ` Catonano
2020-05-09 16:41 ` Catonano
2020-05-09 17:14 ` Tobias Geerinckx-Rice
2020-05-09 17:52 ` Catonano [this message]
2020-05-09 18:12 ` Tobias Geerinckx-Rice
2020-05-09 18:31 ` Catonano
2020-05-09 21:28 ` Vincent Legoll
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=CAJ98PDzHMcgqxwWR9_Hik-LhaXJYt8ptuKXf7uLb2tE0a3UYXQ@mail.gmail.com \
--to=catonano@gmail.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.
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.