Re: a gnome question (fwd)

[James Henstridge <james daa com au>]

Well there aer a few things.  What if the system administrator installs a
new gnome component, and wants to change the default setup.  If you rely
on the skeleton directory, the sysadmin would have to add this default
config file to each user's home directory.  With this system, they would
just put the defaults in one location, and the job would be finished.

My patch also adds a directory $(datadir)/gnome/config-override, where the
sys admin could put config files that would override the user's settings.
For instance, a sys admin wanted to enforce the use of proxies in GnoRPM
for all users, they would create a file
$(datadir)/gnome/config-override/gnorpm, which contains the lines:
  [rpmfind]
  http-proxy=http://proxy:port/
  ftp-proxy=http://proxy:port/

This way the user could change any setting except the proxies.

This patch does not break compatibility, so when it is applied, you will
be able to do this for all applications.

James.

--
Email: james@daa.com.au
WWW:   http://www.daa.com.au/~james/


On Tue, 30 Mar 1999, Adrian Hosey wrote:

>: 
>: So this sort of thing will be easy in the future (get the config right,
>: then copy the config files to $(datadir)/gnome/config), but I am not sure
>: if it is possible right now.
> 
> How about getting the config right for a sample user and then copying
> that ~/.gnome directory into the skeleton dir for useradd/adduser?
> Then it automatically appears as the default for any new user.
> 
>      - A
> 
> 
> -- 
>         FAQ: Frequently-Asked Questions at http://www.gnome.org/gnomefaq
>          To unsubscribe: mail gnome-list-request@gnome.org with 
>                        "unsubscribe" as the Subject.
>