Re: silly problems with program directory

[David Nečas (Yeti) <yeti physics muni cz>]

On Thu, Jun 08, 2006 at 12:04:01PM -0500, Jan Struyf wrote:
> You might also want to consider this:
> <http://autopackage.org/docs/binreloc/>
>
> It allows one to create a binary that can just be unzipped at any place in 
> the filesystem and figures out at runtime where the data files are based 
> on the location of the executable.

Under what provisions?  We've been talking about symlinks,
they are relatively easy to compensate for.  If I hardlink
the binary instead what it can do to find the original
installation path beside scanning the complete filesystem?
Can one have relocability of complete packages and
relocability of just the executable at the same time?

In addition, Unix software is typically much more
cooperative than those installers that live in their own
world and come with their own copy of every other library in
the Universe.  If your software provides something other
programs can use -- shared libs, executables, data, whatever
-- the crucial question is not how it can find itself but
how *other* programs can find and use it.  And that's
why standard install locations are good.

Yeti


--
Anonyms eat their boogers.