If there had been a separate "--localconfdir" choice I would have been
able to decide, on a per-package basis without having to patch it,
whether or not I wanted it to live under /usr, or /etc, or wherever.
I think you are mixing two issues that ought to be separate.
1. Whether the program should make a special subdirectory to contain
its config files.
2. Where the config files, or alternatively that subdirectory, should go.
I think it is fine if #1 is decided by the developer. I don't think
it needs to be customizable. Meanwhile, --sysconfdir specifies #2.
So the only question is, should we change the default for --sysconfdir?
I see the advantage of putting system configuration files in /etc.
The question is, is there any screw in doing so?
- Re: HTML format documentation Alexandre Oliva
- Re: HTML format documentation Harlan Stenn
- Re: HTML format documentation Greg A. Woods
- Re: HTML format documentation Alexandre Oliva
- Re: HTML format documentation Greg A. Woods
- Re: HTML format documentation Peter Eisentraut
- Re: HTML format documentation Greg A. Woods
- Re: HTML format documentation Tom Tromey
- Re: HTML format documentation Greg A. Woods
- Re: HTML format documentation Peter Eisentraut
- Re: HTML format documentation Richard Stallman
- Re: HTML format documentation Greg A. Woods
- Re: HTML format documentation Alexandre Oliva
- Re: HTML format documentation Richard Stallman
- Re: HTML format documentation Alexandre Oliva
- Re: HTML format documentation Thomas E. Dickey
- Re: HTML format documentation Alexandre Oliva
- Re: HTML format documentation Paul D. Smith
- Re: HTML format documentation Richard Stallman
- Re: HTML format documentation Greg A. Woods
- Re: HTML format documentation Richard Stallman
