Bug#615476: general: many binaries are linked with non-existent libtiff.so.3 library
Olaf van der Spek <firstname.lastname@example.org> writes:
> On Mon, Feb 28, 2011 at 1:25 AM, Henrique de Moraes Holschuh
> <email@example.com> wrote:
>>> But there is an ordering choice. local has priority.
>> By default, we assume the local administrator knows what he is doing.
>> That is not going to change.
> Sure. But Sergey has a good point: why are there no bin and lib inside
> /home so normal users can safely install software without risking
> system-wide things to go wrong?
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.