doc: contributing: Move localstatedir instructions.
* doc/contributing.texi (Requirements): Move localstatedir ... (Building from Git): ... here. Change-Id: I860bb7a9e6aea12881469c667496364248293c31master
parent
991f67902f
commit
58646a949a
|
@ -126,23 +126,6 @@ following packages are also needed:
|
||||||
C++11 standard.
|
C++11 standard.
|
||||||
@end itemize
|
@end itemize
|
||||||
|
|
||||||
@cindex state directory
|
|
||||||
@cindex localstatedir
|
|
||||||
@cindex system configuration directory
|
|
||||||
@cindex sysconfdir
|
|
||||||
When configuring Guix on a system that already has a Guix installation,
|
|
||||||
be sure to specify the same state directory as the existing installation
|
|
||||||
using the @option{--localstatedir} option of the @command{configure}
|
|
||||||
script (@pxref{Directory Variables, @code{localstatedir},, standards,
|
|
||||||
GNU Coding Standards}). Usually, this @var{localstatedir} option is set
|
|
||||||
to the value @file{/var}. The @command{configure} script protects
|
|
||||||
against unintended misconfiguration of @var{localstatedir} so you do not
|
|
||||||
inadvertently corrupt your store (@pxref{The Store}). The configuration
|
|
||||||
directory should also be configured by setting the @option{--sysconfdir}
|
|
||||||
option to the @file{/etc} value, which is the location used by Guix to
|
|
||||||
store for example the access control list of authorized machines and the
|
|
||||||
definition of offload machines.
|
|
||||||
|
|
||||||
@node Building from Git
|
@node Building from Git
|
||||||
@section Building from Git
|
@section Building from Git
|
||||||
|
|
||||||
|
@ -245,6 +228,10 @@ export ACLOCAL_PATH=/usr/share/aclocal
|
||||||
@xref{Macro Search Path,,, automake, The GNU Automake Manual}, for
|
@xref{Macro Search Path,,, automake, The GNU Automake Manual}, for
|
||||||
more information.
|
more information.
|
||||||
|
|
||||||
|
@cindex state directory
|
||||||
|
@cindex localstatedir
|
||||||
|
@cindex system configuration directory
|
||||||
|
@cindex sysconfdir
|
||||||
Then, run:
|
Then, run:
|
||||||
|
|
||||||
@example
|
@example
|
||||||
|
@ -259,6 +246,19 @@ normal @code{sysconfdir} value. Note that you will probably not run
|
||||||
important to pass the right @code{localstatedir} and @code{sysconfdir}
|
important to pass the right @code{localstatedir} and @code{sysconfdir}
|
||||||
values, which get recorded in the @code{(guix config)} Guile module.
|
values, which get recorded in the @code{(guix config)} Guile module.
|
||||||
|
|
||||||
|
When configuring Guix on a system that already has a Guix installation,
|
||||||
|
be sure to specify the same state directory as the existing installation
|
||||||
|
using the @option{--localstatedir} option of the @command{configure}
|
||||||
|
script (@pxref{Directory Variables, @code{localstatedir},, standards,
|
||||||
|
GNU Coding Standards}). Usually, this @var{localstatedir} option is set
|
||||||
|
to the value @file{/var}. The @command{configure} script protects
|
||||||
|
against unintended misconfiguration of @var{localstatedir} so you do not
|
||||||
|
inadvertently corrupt your store (@pxref{The Store}). The configuration
|
||||||
|
directory should also be configured by setting the @option{--sysconfdir}
|
||||||
|
option to the @file{/etc} value, which is the location used by Guix to
|
||||||
|
store for example the access control list of authorized machines and the
|
||||||
|
definition of offload machines.
|
||||||
|
|
||||||
Finally, you can build Guix and, if you feel so inclined, run the tests
|
Finally, you can build Guix and, if you feel so inclined, run the tests
|
||||||
(@pxref{Running the Test Suite}):
|
(@pxref{Running the Test Suite}):
|
||||||
|
|
||||||
|
|
Reference in New Issue