This is the mail archive of the
mailing list for the glibc project.
Re: [PATCH] Install config files
- From: ams at gnu dot org (Alfred M. Szmidt)
- To: Allan McRae <allan at archlinux dot org>
- Cc: vapier at gentoo dot org, libc-alpha at sourceware dot org
- Date: Mon, 24 Feb 2014 02:47:08 -0500
- Subject: Re: [PATCH] Install config files
- Authentication-results: sourceware.org; auth=none
- References: <1391870730-6874-1-git-send-email-allan at archlinux dot org> <E1WCAST-0007qR-VQ at fencepost dot gnu dot org> <1994162 dot lQobWGoFXA at vapier> <52F9A871 dot 2010905 at archlinux dot org> <530A8C17 dot 1000805 at archlinux dot org>
- Reply-to: ams at gnu dot org
>>> I find it quite iffy when `make install' in any source tree starts
>>> touching anything in SYSCONFDIR...
>> this is par for the course when it comes to packaging
> Precisely. For all the packages I handle in Arch Linux, glibc is
> really an outlier in terms of requiring its configuration files
> to be manually installed.
> Does anyone really do a "make install" onto the root of their
> system anyway?
If there really is an issue about installing in /etc, perhaps we
could have the relevant programs read config files from
/usr/lib/glibc/foo.conf and that being overridden by /etc/foo.conf
as seems to becoming more common these days.
Since those files are not architecture dependant, they should go in
DATAROOTDIR or somewhere under there, not LIBDIR. And it requires to
modify all things that use those files to also read
What about just `make install-sysconf'? Simple, and easy.