[Pkg-octave-devel] Bug#637787: Bug#637787: Bug#637787: Bug#637787: Bug#637787: trivial fix

[John W. Eaton]

On 23-Aug-2011, Thomas Weber wrote:

| On Mon, Aug 22, 2011 at 02:28:54PM -0400, John W. Eaton wrote:
| > On 19-Aug-2011, Thomas Weber wrote:
| > 
| > | The problem is that dpkg-shlibdeps doesn't like the fact that Octave
| > | uses normal SONAMEs for its libraries now, but ships them in a private
| > | path (so dpkg-shlibdeps doesn't find them and aborts).
| > | So, I'm reading through far too many books/tutorials about libtool and
| > | friends now just so that the libraries end up under /usr/lib.
| > 
| > Octave's Makefile.am files have lines like
| > 
| >   octlib_LTLIBRARIES = liboctave.la
| >   octlib_LTLIBRARIES = liboctinterp.la
| > 
| > so these files are installed in $(octlibdir) and the default
| > definition of octlibdir is set in configure.ac to be
| > 
| >   '$(libdir)/octave/$(version)'
| > 
| > You are of course free to redefine this to be '$(libdir)' instead, and
| > I think that will cause the libraries to be installed into /usr/lib if
| > you set $(prefix) to be /usr.
| 
| Yes, but I don't want to change $(octlibdir), because other software
| might use that for specific libraries. Also, I need to get a better
| understanding of libtool, autoconf and friends anyway.

If you don't want to change octlibdir, then you can change the lines
like

  octlib_LTLIBRARIES = liboctave.la

in the Makefile.am files to be

  lib_LTLIBRARIES = liboctave.la

instead.  It's the octlib (or lib) prefix that is used to generate the
variable that determines the installation directory. 

Maybe we should change the Octave sources to install the Octave
libraries in $libdir instead of $octlibdir?  Or would $pkglibdir be
better?  That is predefined by automake, so writing

  pkglib_LTLIBRARIES = liboctave.la

should cause liboctave to be installed in $(libdir)/@PACKAGE@ (with
"octave" substituted for @PACKAGE@ by configure.

Is the current problem that the libraries are placed in a directory
that has a version number in the name, or does dpkg-shlibeps not find
files in subdirectories of /usr/lib at all?

jwe