> Another solution is to go back to the original configure.in, where we
> didn't have the ${prefix} problem and force the package maker to
> determine the install-path _before_ compilation, so that $sysconfdir
> wouldn't be changed.
Why does the problem occur ? Can anyone explain, why the variables don't
get expanded in the libggi.conf.in and in the source ?
> Perhaps we should provide a script, which asks the package makers,
> which install path he wants to use (of course it should suggest the
> default path). Then the script automatically does the building
> process and generates the package.
Hmm - looks like quite a hack. (not worse than my rpm-from-installed-dirs-
hack, though.
Also please note, that there is the patchlib executable built, which is
intended to allow for patching a binary LibGGI built so that it will
change the path it looks for the primary config file.
CU, Andy
--
Andreas Beck | Email : <[EMAIL PROTECTED]>
