(Jumping into this because of Eric's query on #debian-devel-fr. Please Cc me if you want me to see your replies.)
Andreas Tille (2013-07-10): > > - create a small wrapper (that manages the LD_LIBRARY_PATH) > > - launch freemedforms from the wrapper If that's about avoiding a rpath, that's crazy, and the "solution" is way worse than the "problem" it's trying to solve. > > Should I include the DEB_HOST_MULTIARCH in libs/plugins path? Depends on whether those packages are meant to be coinstallable. > IMHO we should try to support multiarch if there are no strong reasons > not to do this. However, before we ask for new trouble we should > probably resolve the rpath issue which is claimed by lintian (missing > multiarch is not (yet) considered by lintian). Setting RPATH is perfectly OK for plugins, or libraries shared across some binaries from the same package, put into a "private" directory, outside of the default linker search path. (Meaning you don't get to ship shlibs + symbols files, and no other packages are supposed to even know those .so are there.) Mraw, KiBi. -- To UNSUBSCRIBE, email to debian-med-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130720222233.ga32...@mraw.org
