Bug#615476: general: many binaries are linked with non-existent libtiff.so.3 library
> Most software allows this without issues -- just run "./configure
> --prefix=$HOME". You need to adjust $PATH and $LD_LIBRARY_PATH inside
> your shell startup scripts, and you're done.
This will not work. Let's imagine that user have installed some program A
in $HOME. Then user set $LD_LIBRARY_PATH for program A.
Suppoze that A calls some Debian's program B (with "system()" C function
for example). In this case Debian's program B will catch $LD_LIBRARY_PATH
which is incorrect for B, but correct for A.
How many things will be bad if we add rpath=/lib:/usr/lib or rpath=$DEB_LD_LIBRARY_PATH
to all Debian binaries? :-)
By the way: does Debian have step-by-step instructions for system-wide
and user-only installation of non-Debian programs? It is common tasks for any
operating system. So solutions for this tasks must be easy, comfortable