Hi Vincent, Vincent Legoll <vincent.leg...@gmail.com> writes:
>> .config/guix/latest is itself a link into /gnu/store/..., so cannot be >> changed. You should work with a git checkout - so do a "git pull", not >> a "guix pull"! > > The thing I still miss is that: how do I make guix use a different git > checkout ? > > Is there a GUIX_CHECKOUT_PATH env var, a CLI parameter, or > ./boostrap & ./pre-inst-env done in the checkout does all the magic ? I think you are confusing the system you are running (Guix SD) and the system you are developing (the Guix git repo). `.config/guix/latest' is part of the your running system, so it is not the place you want to experiment with changes. To develop Guix, you need to clone its git repo by running: $ git clone git://git.savannah.gnu.org/guix.git Then, you can `cd' into the cloned repo and start running the `./boostrap' stuffs and so on... In case you are new to git, you can read the git book (https://git-scm.com/book/en/v2) or simply search for it on the Internet, Stackoverflow is the place where I learn most of git. Cheers, Alex
