Re: Bug#615476: general: many binaries are linked with non-existent libtiff.so.3 library

[Vincent Danjean <vdanjean@debian.org>]

  Hi,

On 28/02/2011 02:01, Andreas Rottmann wrote:
> 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.
> 
> I'd however strongly suggest not adding any additional directories in
> $HOME by default (e.g. via /etc/skel.d) -- how to organize this should
> be the users' choice.  I for example use
> --prefix="$HOME/.system/stow/<PACKAGE>" for each individual software
> package, so I can quickly remove and reinstate them using GNU
> Stow. Having ~/lib and ~/share, ~/bin, etc. unconditionally created in
> my home directory would just be useless clutter.

I also use stow but in a slightly different way : with your setup,
the software has the knowledge of the stow directory structure.
For examples, it would search its plugins in
$HOME/.system/stow/<PACKAGE>/share/<PACKAGE>
If I try to install other plugins with stow in
$HOME/.system/stow/<PLUGIN_PACKAGE>/share/<PACKAGE>
they won't be found (nor in $HOME/.system/share/<PACKAGE>
where symlinks are created by stow).

So, I configure my software with :
./configure --prefix="$HOME/.system" ...
But I install them with :
make install DESTDIR=$HOME/.system/stow/<PACKAGE>
mv $HOME/.system/stow/<PACKAGE>/$HOME/.system/* $HOME/.system/stow/<PACKAGE>
rmdir --parents $HOME/.system/stow/<PACKAGE>/$HOME/.system
cd $HOME/.system/stow/
stow <PACKAGE>

  Regards,
    Vincent

-- 
Vincent Danjean       GPG key ID 0x9D025E87         vdanjean@debian.org
GPG key fingerprint: FC95 08A6 854D DB48 4B9A  8A94 0BF7 7867 9D02 5E87
Unofficial packages: http://moais.imag.fr/membres/vincent.danjean/deb.html
APT repo:  deb http://people.debian.org/~vdanjean/debian unstable main