unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ng0 <ng0@infotropique.org>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel@gnu.org
Subject: Re: What is the reason for archive keys ending up in /usr?
Date: Fri, 16 Jun 2017 09:33:35 +0000	[thread overview]
Message-ID: <20170616093335.bqfocevlesz6appq@abyayala> (raw)
In-Reply-To: <8760fw8fgs.fsf@elephly.net>

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

Ricardo Wurmus transcribed 0.7K bytes:
> 
> ng0 <ng0@infotropique.org> writes:
> 
> > I was just asking because this seems to differ on systems updated
> > with `guix pull` and those through git. My intended build machine
> > uses /etc/guix/ and the master uses /usr/local/, both are GuixSD.
> > Then /etc/guix is specificed in 'guix pull' updates.
> 
> Who is “the master”?  I assume that you mean the machine using Guix from
> git.
> 
> This is nothing to do with using GuixSD.  If you use Guix from git you
> can affect its behaviour using the “configure” script.  If you do not
> set the prefix it will be the default prefix, which is “/usr/local”.
> The same applies to all other locations, including “localstatedir”.

Okay, then my mistake so far was to not include the prefix in my
update script.

Thanks for clearing that up.
-- 
ng0
OpenPG: A88C8ADD129828D7EAC02E52E22F9BBFEE348588
https://krosos.org/~/ng0/ https://www.infotropique.org

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

      reply	other threads:[~2017-06-16  9:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-15 17:11 What is the reason for archive keys ending up in /usr? ng0
2017-06-16  8:27 ` Ricardo Wurmus
2017-06-16  8:39   ` ng0
2017-06-16  9:11     ` Ricardo Wurmus
2017-06-16  9:33       ` ng0 [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=20170616093335.bqfocevlesz6appq@abyayala \
    --to=ng0@infotropique.org \
    --cc=guix-devel@gnu.org \
    --cc=rekado@elephly.net \
    /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).