Re: Bug#615476: general: many binaries are linked with non-existent libtiff.so.3 library
On Wed, 02 Mar 2011, Tollef Fog Heen wrote: > ]] Henrique de Moraes Holschuh > > | Actually, we usually use it to *remove* bogus rpath, but hey, it would > | be a poor tool if it couldn't be used to add a proper rpath :) > > It doesn't know how to add an rpath, just change or remove one. Patches > gladly accepted. :-) Erk. Heh, what do you know, the world *really* is biased against rpath :-) -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110304201550.gf15...@khazad-dum.debian.net
Re: Bug#615476: general: many binaries are linked with non-existent libtiff.so.3 library
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/" 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//share/ If I try to install other plugins with stow in $HOME/.system/stow//share/ they won't be found (nor in $HOME/.system/share/ 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/ mv $HOME/.system/stow//$HOME/.system/* $HOME/.system/stow/ rmdir --parents $HOME/.system/stow//$HOME/.system cd $HOME/.system/stow/ stow Regards, Vincent -- Vincent Danjean GPG key ID 0x9D025E87 vdanj...@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 -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4d6cb977.1030...@debian.org
Processed: Re: Bug#615476: general: many binaries are linked with non-existent libtiff.so.3 library
Processing commands for cont...@bugs.debian.org: > severity 615476 important Bug #615476 [general] general: many binaries are linked with non-existent libtiff.so.3 library Severity set to 'important' from 'grave' > tag 615476 + unreproducible Bug #615476 [general] general: many binaries are linked with non-existent libtiff.so.3 library Added tag(s) unreproducible. > thanks Stopping processing here. Please contact me if you need assistance. -- 615476: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=615476 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.129874587210895.transcr...@bugs.debian.org
