[Pkg-octave-devel] Multi-archifying Octave
sebastien.villemot at ens.fr
Wed Feb 29 17:40:50 UTC 2012
"John W. Eaton" <jwe at octave.org> writes:
> On 29-Feb-2012, Sébastien Villemot wrote:
> | This should indeed be enough for Octave core.
> | But, as already noted by Thomas Weber, this does not address the issue
> | for add-on packages, because pkg.m hardcodes the arch-specific paths
> | (see the getarch() function there).
> I'm not sure what is best for that. Do you have any suggestions?
> What change are you using for Debian?
The only change that we made is that at configure time we give
--libdir=/usr/lib/<triplet> (where <triplet> is x86_64-linux-gnu on my
system) instead of --libdir=/usr/lib previously. No more. Debian is
progressively making this change in all its packages, since multi-arch
is a release goal for the next version of Debian .
The only annoyance in the case of Octave is that there are now two
triplets in the path of most arch-specific files, and in addition these
triplets are different (Debian use slightly different triplets than
GNU's). But we have decided to live with that for now. Functionally it
should not a problem, since changing --libdir is supported by
Octave. And removing the extra triplet would imply a substantial patch
to pkg.m, which I personally consider--as you do--as an undesirable
Researcher in Economics & Debian Maintainer
Phone: +33-1-40-77-84-04 - GPG Key: 4096R/381A7594
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 835 bytes
Desc: not available
More information about the Pkg-octave-devel