[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#22629: [PATCH 0/4] 'guix pull' produces a self-contained Guix
From: |
Ludovic Courtès |
Subject: |
bug#22629: [PATCH 0/4] 'guix pull' produces a self-contained Guix |
Date: |
Wed, 06 Jun 2018 22:49:45 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/26.1 (gnu/linux) |
Konrad Hinsen <address@hidden> skribis:
>>> I am looking for a reasonably straightforward way to have everything in
>>> my Guix universe (the guix command line tool, emacs-guix, guile, geiser,
>>> ...) consistently use my personal version of the package definitions.
>>
>> Would ‘guix package --manifest’ suffice? Perhaps along with ‘guix pull
>> --commit=XXX’?
>
> 'guix pull --commit=XXX' would be of use if it works with an URL
> pointing to a local repository (haven't tried yet). I'd also
> have to point GUILE_LOAD_PATH to wherever 'guix pull' stores the source
> code tree, which looks doable as well if that's a stable location.
You can already run “guix pull --commit=X --url=$PWD” or similar, and
modules currently end up ~/.config/guix/latest.
Cheers,
Ludo’.
bug#22629: [PATCH 0/4] 'guix pull' produces a self-contained Guix, Fis Trivial, 2018/06/05
bug#22629: [PATCH 0/4] 'guix pull' produces a self-contained Guix, Ludovic Courtès, 2018/06/09