[Pkg-octave-devel] Bug#510579: octave3.0: please put runtime libraries in /usr/lib, not /usr/lib/octave-VERSION

[Rafael Laboissiere]

* Rafael Laboissiere <rafael at debian.org> [2009-03-17 00:16]:

> * Cédric Boutillier <cedric.boutillier at gmail.com> [2009-03-16 14:53]:
> 
> > I found this bug, trying to package for myself octave-ruby [0], an
> > interface between Octave and Ruby.
> > I do not know if what I will say makes much sense, but is it possible
> > to make the octave3.0 package send a file /etc/ld.so.conf.d/octave.conf
> > containing
> > 
> > 	/usr/lib/octave-x.y.z/
> > 
> > so that programs linked against liboctinterp.so, liboctave.so  and libcruft.so 
> > can find these libraries at runtime?
> 
> This sounds like a good idea.  Does it really fix your packaging problem
> with octave-ruby?
> 
> > I think it is what r-base-core is doing.
> 
> Yes, it is.

A thread started yesterday in debian-policy [1] about the use of
/etc/ld.so.conf.d/.  It seems that the Policy people are against the use
of this ldconfig feature.  Let us see if a consensus is reached in this
discussion.

[1] http://lists.debian.org/debian-policy/2009/03/msg00147.html 
 
-- 
Rafael