[Pkg-octave-devel] Bug#637787: Bug#637787: Bug#637787: Bug#637787: Bug#637787: Bug#637787: trivial fix
Thomas Weber
tweber at debian.org
Thu Sep 1 19:03:57 UTC 2011
On Tue, Aug 23, 2011 at 12:24:17PM -0400, John W. Eaton wrote:
> 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.
I'm understanding that now. Thanks for helping.
> 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?
That's a good question; I'm not really sure.
I don't think however, that the version should be in the installation
path - what happens when 3.4.3 comes around?
You should take my words on this with a grain of salt, though. I'm new
to it myself.
Thomas
More information about the Pkg-octave-devel
mailing list