unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Marius Bakke <mbakke@fastmail.com>
To: Reza Alizadeh Majd <r.majd@pantherx.org>, help-guix@gnu.org
Subject: Re: Installing Guix from source
Date: Sun, 14 Jul 2019 19:24:50 +0200	[thread overview]
Message-ID: <87a7dg7cm5.fsf@devup.no> (raw)
In-Reply-To: <28c42c19-88ce-45b4-819c-c19bf086722a@www.fastmail.com>

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

"Reza Alizadeh Majd" <r.majd@pantherx.org> writes:

> Hi Guix, 
>
> I tried to build Guix from source on an existing version of GuixSD.  so I followed 
> the instructions provided in official documents: 
>
> https://guix.info/manual/en/html_node/Requirements.html
> https://www.gnu.org/software/guix/manual/en/html_node/Building-from-Git.html
>
> after build finished, I had two versions of Guix on my machine, the old one which
> is located in store, and the new one  which is installed in `/usr/local/bin`. 
>
> the problem is that the old instance of guix is detected as default on my machine. 
> since I performed a series of  modifications on this new version, like changing the 
> default channels and substitute servers, I need to replace old instance of Guix 
> completely with this new one. 
>
> Does anyone knows how can I perform this replacement? 

If you have made git commits out of your changes, you can do `guix pull
 --url=/your/guix/checkout`.  Otherwise you can use the './pre-inst-env'
 script, as described in the link above.

"./pre-inst-env guix system reconfigure my-config.scm" will create a new
system generation using only code from the git repository.

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

  parent reply	other threads:[~2019-07-14 17:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-14  5:46 Installing Guix from source Reza Alizadeh Majd
2019-07-14  8:50 ` Ricardo Wurmus
2019-07-14 10:39   ` Reza Alizadeh Majd
2019-07-14 17:24 ` Marius Bakke [this message]
2019-07-15 15:05   ` Reza Alizadeh Majd

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=87a7dg7cm5.fsf@devup.no \
    --to=mbakke@fastmail.com \
    --cc=help-guix@gnu.org \
    --cc=r.majd@pantherx.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.
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).