"John W. Eaton" <jwe@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 [1]. 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 thing. [1] http://wiki.debian.org/ReleaseGoals/MultiArch -- Sébastien Villemot Researcher in Economics & Debian Maintainer http://www.dynare.org/sebastien Phone: +33-1-40-77-84-04 - GPG Key: 4096R/381A7594
Attachment:
pgpLkc4OyrEdz.pgp
Description: PGP signature