Re: Re: PROPOSAL: /opt/<provider>/<package>/]

In message <[email protected]>, Bart Whiteley
<[email protected]> writes
>Hello George, others. 
>
>This is my first post, so bear with me.  I've been working with 
>Doug Beattie on these issues.  I don't know how many of my 
>thoughts he has forwarded along. 
>
>
>Also, I would prefer that configuration data be allowed to 
>be in /etc/opt/<provider>/<something>, where <something>
>does not necessarily correspond to a "package".  Similar 
>arguments apply here.  Perhaps there are some configuration
>files that are used by a lot of "packages".  

Do we need the opt/ bit here? Surely /etc/<provider>/ is enough?
>
>I don't think that this increased flexibility violates the spirit
>of what the standard is trying to accomplish.  As long as files
>are under {,/etc,/var}/opt/<provider>, namespace collisions
>will be avoided (it then becomes the responsibility of the 
><provider> to avoid collisions under these directories between
>their own packages, just as it is their responsibility to avoid 
>collisions between init scripts named /etc/init.d/<provider>-*). 
>
>As an example, I would prefer that a company could develop 
>LSB compliant applications WRT the FHS by following
>these simple guidelines:
>
>- All static data be under /opt/<provider>
>- All host-specific configuration data be under /etc/opt/<provider>
>- All variable data be under /var/opt/<provider>
>- Any file or directory that does not comply with one of the first three, 
>  must be prefixed with "<provider>-" (and must have a very good 
>  reason why it doesn't comply with one of the first three). 
>
All user-specific data should be under ~/etc/<provider>/

I don't think this'll be too popular, but I personally do not like the
way my ~ directory gets stuffed horribly full with all those dratted
config files. Yes I know they're mostly dot-files, so not listed by
default, but the point is I *have* to use my home directory, and finding
it stuffed full of unwelcome clutter is not appreciated (especially as a
lot is put there by my distro for stuff I never use, as far as I can
make out). If it had to go in ~/etc, at least I have the choice of going
into that "room" or not, rather than tripping over all the junk left in
the hall :-)

Personally I think that the location of user-specific files should
actually be an option in the system-specific file, but it'll be bad
enough trying to persuade programmers to put stuff in ~/etc, without
persuading them to alter their configs, too.

Cheers,
Wol
-- 
Anthony W. Youngman <[email protected]>
'Yings, yow graley yin! Suz ae rikt dheu,' said the blue man, taking the 
thimble. 'What *is* he?' said Magrat. 'They're gnomes,' said Nanny. The man 
lowered the thimble. 'Pictsies!' Carpe Jugulum, Terry Pratchett 1998
Visit the MaVerick web-site - <http://www.maverick-dbms.org> Open Source Pick