Re: /run and needing a --rundir for configure

[Paolo Bonzini]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Il 05/09/2013 23:43, Eric Blake ha scritto:
> On 09/05/2013 03:25 PM, Karl Berry wrote:
>> Hi Doug,
>> 
>> Subject: /run and needing a --rundir for configure ... The
>> reality is that configure should add --rundir ... ... 
>> http://lwn.net/Articles/436012/
>> 
>> Interesting. rms will need to approve such a change to the coding
>> standards.
>> 
>> Before I ask him: Stefano and autoconf-maintainers, what do you
>> think?
> 
> As one of the autoconf maintainers, I'm in favor of the idea (hence
> my proposed wording patch to make-stds.texi; I also already have a
> scratch patch in my local tree for autoconf, but don't want to push
> it unless the GNU Coding Standards justify its use).  Automake
> would also need a tweak to add run_DATA alongside its existing
> localstate_DATA primary.

This would be the main benefit, and alone is a good reason to add
- --rundir.

Distros tend to use a macro for their configure invocation, hence I
don't think distros are very likely to build with --rundir; current
configure scripts give an error for that option.  This is another
reason why they have to keep the /var/run symbolic link.

Paolo

> As explained in the lwn article, /var is for persistent runtime
> data, while /run is for volatile runtime data; while systems will
> have to provide /var/run as a pointer to /run for the foreseeable
> future (for the sake of projects not actually built with the new
> --rundir support in their configure scripts), it's better to
> differentiate between the semantics up front and make it easier to
> change the destinations at configure time.  And while the default
> should remain unchanged (installation via --prefix=$HOME will still
> use $HOME/var/run if --rundir was not specified), the existence of
> --rundir allows for a system where policy does not change between a
> directory and its children (Lennart has a point that having
> /var/run use tmpfs while /var does not is awkward).



-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBAgAGBQJSKa0uAAoJEBvWZb6bTYbyxCUP/29gr6YNKOVu0Qipx9Hkn3z8
JsJ42ZatIvUuWu3PjxTsBaX1wD4I+biGm3w7HZTZhLm/pogo4o9YqOCEwOAzDSFb
LbTZ8sRClFruoEkT9JuEBp1roH237NuLAaEaUqaXDpJVEptApscFXfFBfLN3z9gu
ZKjfwI1WNihUk1u0oTt27DLbOSE9SFCBQD9Vp7if4GjkmxDlqTcguxtCnSkInJyK
K9jPcutI/8rofmXOKKK68AznddSILTx9Q3C7QdiI3ZBQmjYWFEfR3302owkriTzm
I5EZ3kkvkKTKWuvXLyiBhWpVjtqaKBUfl+xUwsJBDsHtEaWcoaGS0Mq9NWTqwchO
M+XEcZ/gVKGilBoMXPIaQ8hnqm4p9nXFNOmymCqK3NduNz3J/5QZd2NoIJu/fDx/
wYNFLrigzEt4ygUVts5HSIOPC5/f6rKXXRfslB2YsogzJemUPT/dSyamAJoz06nz
uz0IaCYg8CEZHlqgMrciZqWI55XURdkews93I86uPGWeoiQoGE5Yr4JAjmLi/bxB
ounN5NdyXnXUoaQ+g8roH5WGpwlt1Ze65bgGXayVoTiCMKBpqFWRhwSTuT/x+qng
Ewmfl/jn+lY3FE3OYfi55xNotcfmIAH8qHsg6VfVMiu42H8eAzrnL3q8Rs2xtvNg
5esRJTHIXI+Zng05DxFa
=sCsp
-----END PGP SIGNATURE-----