On Jul 3, 2007, at 11:53 AM, Ralf S. Engelschall wrote:
On Tue, Jul 03, 2007, Mark Hatle wrote:
Jeff Johnson wrote:
IMHO, this is the wrong fix.
per-system configuration belongs in the per-system configuration
directory, which is /etc everywhere.
<scarcasm>
Or perhaps I missed some n00bie FHS proposal for uglix ...
</scarcasm>
On my cross development system, /etc is untouchable.. because it
requires root. So we have it configured to be in a location the user
can modify it.
This is one of the reasons it's nice that it's now the SYSCONFIG
directory instead of hard coded to /etc. (I have local patches that
take it one step further and allow for the run-time relocation....
but
thats beyond this scope.)
Jeff, this change was motivated by two reasons: 1. I simply wanted
that _all_ hard-coded path can be at least optionally be overridden
for consistency(!) reasons, and 2. the definition of "system" here
cannot mean just a hard-coded /etc as for many situations "system"
could also mean /usr/local/etc (FreeBSD) or (in the OpenPKG world)
even <prefix>/etc where <prefix> is an arbitrary choosen location. As
the Linux people usually do not technically distinguish between base
system and addons, they might think a simple hard-coded /etc is fine.
But outside the Linux world people often have _multiple_ "system"
areas
(base system, addons, etc). And there /etc is just the "classical"
one...
PS: The _default_ for SYSCONFIGDIR is still /etc/rpm, of course!
I've not touched this as it is clear I would been punished...
Understood. I'm just using you as practice discussion (because you're
reasonable ;-)
before I try to squat /etc/rpm.
Multiple per-system config files is what is senseless, not the path
value. Any single
valued path will do, /etc is the usual convention.
73 de Jeff
______________________________________________________________________
RPM Package Manager http://rpm5.org
Developer Communication List rpm-devel@rpm5.org
