Jason Sikes wrote:
> You are correct that the
> configuration files should only go in one directory when done on behalf
> of a distribution.
OK, this removes my biggest worry.
> >* worse, invites packages to (perhaps inadvertently) restrict user
> > freedom.
>
> Restricting user freedom i
> >- Packages define a configure option for the /etc directory, e.g.
> >--enable-etcdir=/etc
> > through Autoconf [3].
> Yes, and what we are proposing is that this option (by a different name)
> will be included in Autoconf so that developers don't have to add it
We should also be very careful when adding new --foodir options, this
breaks things quickly (old ./configure will error for example -- so if
you want a single line for all invocations, you'll now have to remeber
what is what version of autoconf!).
On 2/7/23 15:44, Bruno Haible wrote:
On 2023-02-06 08:30, Valentin Lefebvre wrote:
This patch add a new autoconf argument that allows installation
into the vendor configuration directory (/usr/etc/). Some linux
distribution now move system configuration files from /etc to /usr/etc.
See t
Alfred M. Szmidt wrote:
>>The configure --help output and/or the documentation should state that
>> - "make install" will install into SYSCONFDIR,
>
> It should absolutley not state that. It is on purpose that `make
> install' does not trash sysconfdir
Well, at least 178 packages do ins
