Re: The tricky case of "--localstatedir=/var"

On Thu, Mar 17, 2016 at 11:11:40PM +0100, Ludovic Courtès wrote: > However, for the purpose of avoiding bad surprises (configuring Guix > with the wrong localstatedir), I thought we could have a ‘configure’ > check that would compare the chosen localstatedir with the current > installation’s locals

Re: The tricky case of "--localstatedir=/var"

Jookia <166...@gmail.com> skribis: > Over the past month a few people (myself included) have been hit by the > 'gotcha' > of not running ./configure with "--localstatedir=/var". As discussed on IRC, the expected default values are specified in

Re: The tricky case of "--localstatedir=/var"

l...@gnu.org (Ludovic Courtès) skribis: > As discussed on IRC, the expected default values are specified in > . > I think it’s reasonable to keep following these rules. > > However, for the purpose of avoiding bad surprises (con

Re: The tricky case of "--localstatedir=/var"

Jookia <166...@gmail.com> skribis: > On Thu, Mar 17, 2016 at 11:11:40PM +0100, Ludovic Courtès wrote: >> However, for the purpose of avoiding bad surprises (configuring Guix >> with the wrong localstatedir), I thought we could have a ‘configure’ >> check that would compare the chosen localstatedir

Re: The tricky case of "--localstatedir=/var"

l...@gnu.org (Ludovic Courtès) writes: > Jookia <166...@gmail.com> skribis: > >> Over the past month a few people (myself included) have been hit by the >> 'gotcha' >> of not running ./configure with "--localstatedir=/var". > > As discussed on IRC, the expected default values are specified in > <

Re: The tricky case of "--localstatedir=/var"

On Fri, Mar 18, 2016 at 07:45:55PM +0100, Ludovic Courtès wrote: > Sorry for being slightly disorganized, but could you give me the link to > that patch? :-) Here it is: https://lists.gnu.org/archive/html/guix-devel/2016-03/msg00386.html > Could you explain how that would work? Not sure what v

Re: The tricky case of "--localstatedir=/var"

On Wed, Feb 17, 2016 at 05:50:31PM +, Chris Marusich wrote: > I understand why it's > nice to have the Guix package so that you can easily work with its > dependencies, but isn't "guix pull" the recommended way to keep your Guix > installation up to date? As far as I know, the only ways of get

Re: The tricky case of "--localstatedir=/var"

On Wed, Feb 17, 2016 at 05:50:31PM +, Chris Marusich wrote: > I see. Please indulge my curiosity. You said that you "compile Guix from > source instead of using the official > binaries, then install Guix so it's managed by Guix." Do you do this on > GuixSD, or on a foreign distribution? Do you

Re: The tricky case of "--localstatedir=/var"

I see. Please indulge my curiosity. You said that you "compile Guix from source instead of using the official binaries, then install Guix so it's managed by Guix." Do you do this on GuixSD, or on a foreign distribution? Do you mean that you first compile and install Guix somewhere on your system, a

Re: The tricky case of "--localstatedir=/var"

On Wed, Feb 17, 2016 at 01:15:17AM -0800, Chris Marusich wrote: > It looks like the decision to explicitly set localstatedir to "/var" in > the guix package was made in commit 2d195e67 by Ludo. Perhaps he can > explain what his intent was. That'd be nice. I'm sure there's a reason which could be h

Re: The tricky case of "--localstatedir=/var"

Mark H Weaver writes: > Danny Milosavljevic writes: > >> also, even worse, when using a fine git checkout for some time, you will >> from time to time do this: >> >> $ git pull >> $ make check >> >> If this touches stuff autoconf cares about, make will do ./configure >> again and leave localst

Re: The tricky case of "--localstatedir=/var"

Jookia <166...@gmail.com> writes: > the Guix package doesn't use this default which breaks compatibility > with itself. Ah, I see what you're saying. I think you're saying that the guix package (defined in gnu/packages/package-management.scm) explicitly sets the localstatedir to "/var", even thou

Re: The tricky case of "--localstatedir=/var"

On Wed, Feb 17, 2016 at 12:06:25AM -0800, Chris Marusich wrote: > I'm not sure there is a single default that will work for everybody. In > general, a value that is appropriate for one use case will not be > appropriate for a different use case. I hope I'm not implying that a single default will w

Re: The tricky case of "--localstatedir=/var"

Jookia <166...@gmail.com> writes: > Over the past month a few people (myself included) have been hit by the > 'gotcha' > of not running ./configure with "--localstatedir=/var". It doesn't say this in > the documentation but I question whether not having it as /var is a sane > default. I'm sure th

Re: The tricky case of "--localstatedir=/var"

Danny Milosavljevic writes: > also, even worse, when using a fine git checkout for some time, you will from > time to time do this: > > $ git pull > $ make check > > If this touches stuff autoconf cares about, make will do ./configure > again and leave localstatedir off. Then lots (32) of the te

Re: The tricky case of "--localstatedir=/var"

Hi, also, even worse, when using a fine git checkout for some time, you will from time to time do this: $ git pull $ make check If this touches stuff autoconf cares about, make will do ./configure again and leave localstatedir off. Then lots (32) of the tests will fail. Just happened again...

Re: The tricky case of "--localstatedir=/var"

Jookia writes: > Hey there, > > Over the past month a few people (myself included) have been hit by the > 'gotcha' > of not running ./configure with "--localstatedir=/var". It doesn't say this in > the documentation but I question whether not having it as /var is a sane > default. I'm sure this i

Re: The tricky case of "--localstatedir=/var"

On Wed, Feb 17, 2016 at 04:12:32AM +1100, Jookia wrote: > I'm not sure how that would really fix the issue that people are hitting: Say > we > move some of the content to /gnu, things like profiles, the daemon socket, all > the things that Guix looks for and symlinks to won't be found if Guix look

Re: The tricky case of "--localstatedir=/var"

On Tue, Feb 16, 2016 at 05:41:09PM +0100, Andreas Enge wrote: > There is also a middle ground that would be possible: Move some of the > content of localstatedir to /gnu; this would make sense for the sqlite > database, for instance. Then it would be possible to copy /gnu from one > system to anoth

Re: The tricky case of "--localstatedir=/var"

On Tue, Feb 16, 2016 at 03:29:02PM +0100, Ricardo Wurmus wrote: > Jookia <166...@gmail.com> writes: > > * Change localstatedir to /var by default. > > * Put the localstatedir in /gnu. > I’m actually doing this on my cluster installation. It’s very > convenient at first because you can just mount

Re: The tricky case of "--localstatedir=/var"

On 16 February 2016 at 17:04, Tobias Geerinckx-Rice wrote: > Hullo Guix, > > On 16 February 2016 at 14:57, Jookia <166...@gmail.com> wrote: >> >> >> * Put the localstatedir in /gnu. >> >> This is actually what Nix does, so I'm a little surprised as to why Guix has >> deviated from this practice.

Re: The tricky case of "--localstatedir=/var"

Hullo Guix, On 16 February 2016 at 14:57, Jookia <166...@gmail.com> wrote: > > > * Put the localstatedir in /gnu. > > This is actually what Nix does, so I'm a little surprised as to why Guix has > deviated from this practice. This will require updating all the patches to use > /gnu/var as the loc

Re: The tricky case of "--localstatedir=/var"

On Tue, Feb 16, 2016 at 03:29:02PM +0100, Ricardo Wurmus wrote: > Is this really so? Could you give us an example please? Oops! I was misreading the git log and patches. I'm wrong on this (happily, I may add!) So no, there's no patches to change. This is strictly a Guix issue. > ~~ Ricardo Jook

Re: The tricky case of "--localstatedir=/var"

Jookia <166...@gmail.com> writes: > Hey there, > > Over the past month a few people (myself included) have been hit by the > 'gotcha' > of not running ./configure with "--localstatedir=/var". It doesn't say this in > the documentation but I question whether not having it as /var is a sane > defa

The tricky case of "--localstatedir=/var"

Hey there, Over the past month a few people (myself included) have been hit by the 'gotcha' of not running ./configure with "--localstatedir=/var". It doesn't say this in the documentation but I question whether not having it as /var is a sane default. I'm sure this is somehow tied to the conventi