On 2011-02-04 10:09:51 -0500, Yaroslav Halchenko wrote: > Without /usr/local/lib64 symlink to /usr/local/lib many local > installations of upstream projects (not that I am encouraging such > cruel activity) would install into /usr/local/lib64 on amd64 > systems. Since symlink is not available, install would create a > directory /usr/local/lib64 to place the content; but default Debian > setup of ldconfig does not include any of */lib64 directories, so > those libraries would not become readily available.
I'd say that such projects are buggy as they do not follow Debian's convention: that's up to the "configure" step to decide what to do, depending on the target system. > Having a symlink /usr/local/lib64 -> /usr/local/lib should make our > systems "friendlier" to the users willing sacrificing piece of mind > by installing something 'locally'. There would still be problems if the administrator or the end user forgets to add symbolic links for other lib directories (e.g. /opt/lib64 -> /opt/lib, $HOME/lib64 -> $HOME/lib, and so on). If not all lib paths are consistent, this also means that incorrect library versions could be selected, as shown here: http://gcc.gnu.org/ml/gcc-help/2010-11/msg00341.html Alternatively, Debian could switch to the standard convention (even though I do not like it, I think this would be a better solution when one needs to deal with upstream projects that do not know about Debian). -- Vincent Lefèvre <vinc...@vinc17.net> - Web: <http://www.vinc17.net/> 100% accessible validated (X)HTML - Blog: <http://www.vinc17.net/blog/> Work: CR INRIA - computer arithmetic / Arénaire project (LIP, ENS-Lyon) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
