I think my postings may have been a little unclear, what I'm
advocating is
this ...
Keep the current scheme of using two levels of .GNUsteprc files with
minor
modifications ...
1. The top-level file can be found in a standard location or in the
location
pointed to be the GNUSTEP_ROOT environment variable (at the moment I
think
it's located in the directory pointed to by GNUSTEP_SYSTEM_ROOT
rather than
any standard location).
2. As at present, allow per-user configuration of paths by a per-user
.GNUsteprc file, *if* the top level file permits it.
Having been round these discussions several times in the past, I'm
pretty
much convinced that this permits the degree of relocatability and
flexibility
people want and also the ability for a sysadmin to securely lock-down
the
path layout too.
The base library would use the information from the .GNUsteprc files
to
provide all path information within applications.
The make package would do the same thing to set its own variables.
We would supply a standard script to set GNUSTEP_ROOT,
LD_LIBRARY_PATH, PATH
... but, as you pointed out, this is a convenience rather than a
necessity.
My area of uncertainly here is how to improve the format of the
.GNUsteprc
files ... we want them simple to understand and easy to parse. In
particular, it would be important to have them in a format in which
it's easy
for the make system to parse them or to use a simple C program or
shell
script to parse them, set values in it's environment, and re-invoke
make.
We may also want to allow for more sophisticated control of per-user
setting
of paths in these files, but I'm not sure that this would be worth
the
effort/complexity - so I'd prefer to leave any complex code out and
add it at
a later date if/when there is
a definite requirement.
Maybe the current format is already good for this (it's certainly
usable) ...
I'm not sure.
_______________________________________________
Bug-gnustep mailing list
Bug-gnustep@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-gnustep