Ken Moffat wrote:

>  On my partial-gnome installation (apart from the gnome2 packages
> previously mentioned, I built gcalctool, gucharmap,
> epiphany{,-extensions}, gstreamer/plugins, totem, yelp from 3.2 -
> plus their many required dependencies) I have the following
> directories in /etc/gnome:
> 
> bonobo-activation, dbus-1, gconf, gnome-vfs-2.0, profile.d, sound,
> xdg.  These are not just conf,desktop,xml files - there are also
> schemas and other odds and sods.  But as long as each goes into a
> directory, what does it matter ?  Using /etc rather than /etc/gnome
> looks much more straightforward.  Also, if you are a gnome user
> (i.e. a much fuller gnome than I build), what does it gain you by
> putting all these directories into /etc/gnome instead of /etc ?
> 
>  I do have *one* file in /etc/gnome : gnome-vfs-mime-magic from
> gnome-mime-data (I installed that for totem, if I recall correctly).
> Since there are other packages which dump files straight into /etc
> (even e2fsprogs in lfs itself) I don't see this as a problem.
> 
>  Having said that, I've noticed that distros such as gentoo put the
> dhclient files in a directory (conf, -exit-hooks) but BLFS has
> always been happy to drop these into /etc so I haven't felt any
> overwhelming urge to alter the client script so that it would find
> the moved hooks.

My only concern is to keep something like the /etc directory at a 
reasonable number of entries.  Right now I have 90.  Compare that to 
ubuntu that has 217 or RHEL with 199.  I think of the /etc directory as 
a place where I may need to browse to figure out a file to update. 
Something like php.ini is OK because it is only one file.  A few more is 
not a problem, but I think 200 is too many.  It just makes sense to me 
to group related functionality together.

   -- Bruce
-- 
http://linuxfromscratch.org/mailman/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Reply via email to