On Mon, 18 Jun 2012 09:27, Stephan Kulow
On 15.06.2012 21:43, Křištof Želechovski wrote:
I have no clue why it cannot find the file.
Because it is not in ldconfig? Exactly, I fixed it in now in arts. arts shouldn't rely on rpaths.
I'd like to rise a question here: Would it be acceptable for a package simply to include a file /etc/ld.so.conf.d/<package>.conf to work around a missing ldconfig entry? Or is for such a file a security audit needed? A example I see on my system would be /etc/ld.so.conf.d/graphviz.conf which is owned by the graphviz - package. Or is there more than a simple file needed? A call to /sbin/ldconfig with [params] perhaps, see example (code from graphviz - package) postinstall scriptlet (using /bin/sh): /sbin/ldconfig # run "dot -c" to generate plugin config /usr/lib64/graphviz/config dot -c test -s /usr/lib64/graphviz/config || echo "/usr/lib64/graphviz/config doesn't exist! Check installation." postuninstall scriptlet (using /bin/sh): /sbin/ldconfig if ! test -x $RPM_INSTALL_PREFIX0/bin/dot; then rm -f $RPM_INSTALL_PREFIX0/lib64/graphviz/config; fi (end of code) Is this the "right" way to go to avoid rpath? -- Yamaban.