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 08:39:25 +0000	[thread overview]
Message-ID: <20170616083925.5l6yxx6oys56olek@abyayala> (raw)
In-Reply-To: <87a8588hi2.fsf@elephly.net>

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

Ricardo Wurmus transcribed 0.5K bytes:
> 
> ng0 <ng0@infotropique.org> writes:
> 
> > user@abyayala ~$ sudo guix archive --generate-key
> > guix archive: error: key pair exists under '/usr/local/etc/guix'; remove it first
> >
> > Is this location picked to keep compability with other Operating Systems?
> > It seems to be the only part of Guix which picks /usr/
> 
> This depends on how you configured Guix.  “/usr/local” is the default
> prefix.  You can override it with “./configure --prefix=/some/other/dir”.
> 
> -- 
> Ricardo
> 
> GPG: BCA6 89B6 3655 3801 C3C6  2150 197A 5888 235F ACAC
> https://elephly.net
> 
> 

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.
-- 
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  8:40 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 [this message]
2017-06-16  9:11     ` Ricardo Wurmus
2017-06-16  9:33       ` ng0

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=20170616083925.5l6yxx6oys56olek@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).