Re: execline-1.05 non-root installation problem

>
> Here's how I do it.  mkmed depends on prjlibs.  So mkmed has a
> conf-compile/depend_prjlibs file, where the user can configure the
> path to prjlibs at build time.  Then the build procedure creates a
> symlink conf/prjlibs pointing to the configured path, and the full
> path to the conf/prjlibs symlink is compiled into the programs.  The
> symlink can be changed later, but beyond that, there is no run-time
> configurability.  This ought to be good enough for most situations.
>
> Now, if mkmed is installed by sp-install, and $SP_ROOT is set, then
> sp-install notices conf-compile/depend_* and edits those files
> appropriately before running package/compile.  The package itself does
> not (and probably should not) know anything about $SP_ROOT.  All the
> needed information is communicated through the conf-compile/* files.
> $SP_ROOT is just a way for the user to tell sp-install how to do what
> the user would have done by hand if they were not using sp-install.
>
> I think it's best to make each dependency path, and the package's own
> path, configurable as described above, and let higher-level tools like
> sp-install handle the more heavy-handed things like $SP_ROOT.  Too
> much magic in package/compile scripts will make sp-install a harder
> problem.
>

As far as I remember, Pauls approach have worked in my previous non-root
installations of his packages.
You have my vote, Paul...

kind regards Uffe