From: Chris Marusich <cmmarusich@gmail.com>
To: Jookia <166291@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: The tricky case of "--localstatedir=/var"
Date: Wed, 17 Feb 2016 17:50:31 +0000 [thread overview]
Message-ID: <CAEKzfH=qb2Qek0Gz-nvE_ppTj89Ze_aPMsp5u2M2yo-E0o639A@mail.gmail.com> (raw)
In-Reply-To: <20160217100857.GA29638@novena-choice-citizen.lan>
[-- Attachment #1: Type: text/plain, Size: 716 bytes --]
I see. Please indulge my curiosity. You said that you "compile Guix from
source instead of using the official
binaries, then install Guix so it's managed by Guix." Do you do this on
GuixSD, or on a foreign distribution? Do you mean that you first compile
and install Guix somewhere on your system, and then run "guix package -i
guix" to install the Guix package into the Guix store? Assuming that's what
you do, which guix-daemon winds up running - the one you installed
originally, or the one you installed into the store? I understand why it's
nice to have the Guix package so that you can easily work with its
dependencies, but isn't "guix pull" the recommended way to keep your Guix
installation up to date?
>
[-- Attachment #2: Type: text/html, Size: 940 bytes --]
next prev parent reply other threads:[~2016-02-17 17:50 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-16 13:57 The tricky case of "--localstatedir=/var" Jookia
2016-02-16 14:29 ` Ricardo Wurmus
2016-02-16 14:52 ` Jookia
2016-02-16 16:41 ` Andreas Enge
2016-02-16 17:12 ` Jookia
2016-02-16 17:16 ` Andreas Enge
2016-02-16 16:04 ` Tobias Geerinckx-Rice
2016-02-16 16:08 ` Tobias Geerinckx-Rice
2016-02-16 19:11 ` Christopher Allan Webber
2016-02-16 19:59 ` Danny Milosavljevic
2016-02-16 22:42 ` Mark H Weaver
2016-02-17 9:29 ` Ricardo Wurmus
2016-02-17 8:06 ` Chris Marusich
2016-02-17 8:38 ` Jookia
2016-02-17 9:15 ` Chris Marusich
2016-02-17 10:08 ` Jookia
2016-02-17 17:50 ` Chris Marusich [this message]
2016-02-17 18:00 ` Jookia
2016-02-17 18:23 ` Andreas Enge
2016-03-17 22:11 ` Ludovic Courtès
2016-03-17 22:19 ` Mathieu Lirzin
2016-03-18 1:12 ` Jookia
2016-03-18 18:45 ` Ludovic Courtès
2016-03-19 3:27 ` Jookia
2016-03-19 14:11 ` Ludovic Courtès
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='CAEKzfH=qb2Qek0Gz-nvE_ppTj89Ze_aPMsp5u2M2yo-E0o639A@mail.gmail.com' \
--to=cmmarusich@gmail.com \
--cc=166291@gmail.com \
--cc=guix-devel@gnu.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).