> It would be nice if libgg could use a LIBGG_PATH environment variable to
> search for config files.
No, that would be horrible. It is a big security hole. LibGGI loads
libraries dynamically, and what libraries are loaded depends on the
config files.
This is not so much an issue for sane targets like X or fbdev, but it is
for SVGAlib, which needs to run as root.
Allowing the user to interfere with the config files basically means instant
root access.
Another place where this would hurt are other suid-programs. I don't
recommend to write suid programs using LibGGI, but it shouldn't be
impossible either.
LibGGI and LibGII have been specifically designed to be binary-patchable
with respect to the config paths to have an easy way to relocate them
despite the above dilemma.
> Seems very worth having if you care at all about testing both
> compilation _and_ execution without installing over the top of your
> stable software.
This can be done, but please by patching while installing or similar. User
controllable Methods are a no-no here.
> I really think this feature is worth adding
See above. That would be a real misfeature IMHO.
> Think of this: You want to run GGI 2.0 stable, but be able to build and
> fully test GGI 2.1 development without clobbering your stable install.
No Problem: You just build and install with $prefix=~/local and set a few
config variables (LD_LIBRARY_PATH e.g.) so that these libs, includes etc.
are used.
CU, Andy
--
= Andreas Beck | Email : <[EMAIL PROTECTED]> =
