Peder Stray <[EMAIL PROTECTED]> writes:
> Mikhael Goikhman <[EMAIL PROTECTED]> writes:
> 
> > Still you didn't described an example where this would be required.
> > I can invent artificial examples, but I want to see a real-life one
> > where using FVWM_DATADIR for system stuff and FVWM_USERDIR for
> > user's is not enough.
> 
> we (that is Institute for Informatics, University of Oslo, Norway)
> have sitewide fvwm setup for all new users. Installed on at least 2
> different architectures as of now... using a highly modularised setup,
> where users can customize parts of the setup by making their own files
> in FVWM_USERDIR, these would otherwise be included from the global
> setup directory (same for all architectures). Other stuff from the
> fvwm distribution would be included from FVWM_DATADIR.

Is there a reason you don't want to put the global stuff in
FVWM_DATADIR?

-- 
Dan Espen
444 Hoes Lane  Room RRC 1C-214           E-mail: [EMAIL PROTECTED]
Piscataway, NJ 08854                     Phone: (732) 699-5570
--
Visit the official FVWM web page at <URL:http://www.fvwm.org/>.
To unsubscribe from the list, send "unsubscribe fvwm-workers" in the
body of a message to [EMAIL PROTECTED]
To report problems, send mail to [EMAIL PROTECTED]

Reply via email to