Now you explained how, not why.
The only site wide settings I see any point with are ones that make Pike modules that are installed in site specific places accessible under as standard names as possible in the module tree. They should only extend the namespace, not alter it. I believe setting PIKE_MODULE_PATH in /etc/environment or similar is enough to accomplish it. The reason why a site administrator might want to split up the module tree in different locations is the usual sysadm issues, e.g. local vs shared file systems, backuped volumes, etc.
/ Martin Stjernholm, Roxen IS
Previous text:
2002-09-03 23:41: Subject: the Pike module system
thie site-wide would provide only a default configuration, tunable/tweakable on the basis you described. The default could also be the Pike upstream default - i.e. no local changes at all.
/ Marek Habersack (Grendel)