bug#22629: [PATCH 0/4] 'guix pull' produces a self-contained Guix

Hello Chris, Thanks for your feedback! Chris Marusich skribis: > I was surprised that "guix pull" doesn't build the guix package via the > usual mechanisms (e.g., the way it would be built if I ran "guix build > guix"). The new "guix pull" code builds a profile, so it seems like we > could

bug#22629: [PATCH 0/4] 'guix pull' produces a self-contained Guix

Hi Ludo, Ludovic Courtès writes: > Here is the “new” ‘guix pull’ that we discussed notably in this thread: > > https://bugs.gnu.org/22629 Although I've been enjoying the new guix pull for a while now, I just today found the time to take a peek at these code changes. It's always educational

bug#22629: bug#28471: closed (Re: bug#22629: [PATCH 0/4] 'guix pull' produces a self-contained Guix)

Hello! > • Meta-data about what was pulled is kept in manifest entries, using > the ‘properties’ discussed in . > Currently the UI doesn’t use it but you can see that info in > ~/.config/guix/current/manifest. Commit

bug#22629: [PATCH 0/4] 'guix pull' produces a self-contained Guix

Hello Guix! Ludovic Courtès skribis: > Here is the “new” ‘guix pull’ that we discussed notably in this thread: > > https://bugs.gnu.org/22629 > > The major difference is that instead of just building a bunch of modules > and putting them under ~/.config/guix/latest, it now produces a >

bug#22629: [PATCH 0/4] 'guix pull' produces a self-contained Guix

> >>> The result of running ‘guix pull’ is a “profile” available under >>> ‘~/.config/guix/current’ containing the latest Guix. Thus, make sure to >>> add it to the beginning of your search path so that you use the latest >>> version, and similarly for the Info manual (*note

bug#22629: [PATCH 0/4] 'guix pull' produces a self-contained Guix

Konrad Hinsen 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?

bug#22629: [PATCH 0/4] 'guix pull' produces a self-contained Guix

Hi Ludo, >> Fine, so if I run update-guix-package.scm and then do the install, I get >> what I expect, right? > > Yes (even with current ‘master’), but it’s quite heavyweight since you > end up recompiling all of Guix. Not great, but doable from time to time. >> I am looking for a reasonably

bug#22629: [PATCH 0/4] 'guix pull' produces a self-contained Guix

Hello! Fis Trivial skribis: >> The result of running ‘guix pull’ is a “profile” available under >> ‘~/.config/guix/current’ containing the latest Guix. Thus, make sure to >> add it to the beginning of your search path so that you use the latest >> version, and similarly for the Info

bug#22629: [PATCH 0/4] 'guix pull' produces a self-contained Guix

Hello Konrad, Konrad Hinsen skribis: >>> Just wondering: does this mean that I could substitute Guix from my local >>> source tree simply by doing >>> >>>./pre-inst-env guix package -p ~/.config/guix/current -i guix >> >> That would just install the snapshot that the ‘guix’ package refers

bug#22629: [PATCH 0/4] 'guix pull' produces a self-contained Guix

Hi, first of all, thanks for the improvement. It's really exciting know progress in guix. But I have a few questions around this change. Just curiosity. :) > Hello Guix! > > Here is the “new” ‘guix pull’ that we discussed notably in this thread: > > https://bugs.gnu.org/22629 > > The major

bug#22629: [PATCH 0/4] 'guix pull' produces a self-contained Guix

Hi Ludo, >> Just wondering: does this mean that I could substitute Guix from my local >> source tree simply by doing >> >>./pre-inst-env guix package -p ~/.config/guix/current -i guix > > That would just install the snapshot that the ‘guix’ package refers to > (it’s defined in (gnu packages

bug#22629: [PATCH 0/4] 'guix pull' produces a self-contained Guix

On Sun, Jun 03, 2018 at 10:29:43PM +0200, Ludovic Courtès wrote: > Pjotr Prins skribis: > > > On Fri, Jun 01, 2018 at 02:13:10PM +0200, Ludovic Courtès wrote: > >> Thanks for your support! We’ll still have to make the whole build > >> process faster but yeah, that’s one important step towards

bug#22629: [PATCH 0/4] 'guix pull' produces a self-contained Guix

Hello! Konrad Hinsen skribis: > Just wondering: does this mean that I could substitute Guix from my local > source tree simply by doing > >./pre-inst-env guix package -p ~/.config/guix/current -i guix That would just install the snapshot that the ‘guix’ package refers to (it’s defined in

bug#22629: [PATCH 0/4] 'guix pull' produces a self-contained Guix

Pjotr Prins skribis: > On Fri, Jun 01, 2018 at 02:13:10PM +0200, Ludovic Courtès wrote: >> Thanks for your support! We’ll still have to make the whole build >> process faster but yeah, that’s one important step towards 1.0! > > But we do get substitutes in principle, right? Yes, but only for

bug#22629: [PATCH 0/4] 'guix pull' produces a self-contained Guix

On Fri, Jun 01, 2018 at 02:13:10PM +0200, Ludovic Courtès wrote: > Thanks for your support! We’ll still have to make the whole build > process faster but yeah, that’s one important step towards 1.0! But we do get substitutes in principle, right? Pj.

bug#22629: [PATCH 0/4] 'guix pull' produces a self-contained Guix

Heya David, "Thompson, David" skribis: > On Thu, May 31, 2018 at 10:43 AM, Ludovic Courtès wrote: >> Hello Guix! >> >> Here is the “new” ‘guix pull’ that we discussed notably in this thread: >> >> https://bugs.gnu.org/22629 >> >> The major difference is that instead of just building a bunch

bug#22629: [PATCH 0/4] 'guix pull' produces a self-contained Guix

Hello! Ricardo Wurmus skribis: >> The result of running ‘guix pull’ is a “profile” available under >> ‘~/.config/guix/current’ containing the latest Guix. Thus, make sure to >> add it to the beginning of your search path so that you use the latest >> version, and similarly for the

bug#22629: [PATCH 0/4] 'guix pull' produces a self-contained Guix

> Here is the “new” ‘guix pull’ that we discussed notably in this thread: > > https://bugs.gnu.org/22629 > > The major difference is that instead of just building a bunch of modules > and putting them under ~/.config/guix/latest, it now produces a > standalone package (with bin/guix,

bug#22629: [PATCH 0/4] 'guix pull' produces a self-contained Guix

Hi Ludo, > The major difference is that instead of just building a bunch of modules > and putting them under ~/.config/guix/latest, it now produces a > standalone package (with bin/guix, share/info/guix.info, etc.) and puts > it in a profile under ~/.config/guix/current. Quoth the manual: This

bug#22629: [PATCH 0/4] 'guix pull' produces a self-contained Guix

Hey Ludo, On Thu, May 31, 2018 at 10:43 AM, Ludovic Courtès wrote: > Hello Guix! > > Here is the “new” ‘guix pull’ that we discussed notably in this thread: > > https://bugs.gnu.org/22629 > > The major difference is that instead of just building a bunch of modules > and putting them under

bug#22629: [PATCH 0/4] 'guix pull' produces a self-contained Guix

Hello Guix! Here is the “new” ‘guix pull’ that we discussed notably in this thread: https://bugs.gnu.org/22629 The major difference is that instead of just building a bunch of modules and putting them under ~/.config/guix/latest, it now produces a standalone package (with bin/guix,