[Pkg-octave-devel] Bug#682207: Bug#682207: octave: using dpkg-architecture at run time is a bad idea

[Sébastien Villemot]

Andreas Beckmann <debian at abeckmann.de> writes:

> octave depends on dpkg-dev in order to use dpkg-architecture at runtime.
> This is a bad idea. The path that is being computed in this way needs to
> be built into the binary.
>
> The current approach will fail in a multiarch installation of octave:
> dpkg-architecture will report information about the primary
> architecture, but octave may be installed from another architecture and
> will be using a wrong path ...

My understanding is that it is not possible to install a non-multi-arch
aware package (like octave) from another architecture, so that the
scenario that you describe cannot materialize. Am I wrong?

> And the dpkg-dev dependency needs to be dropped.

Why is this dependency a problem (independently of the above issue)?

Thanks,

-- 
 .''`.    Sébastien Villemot
: :' :    Debian Maintainer
`. `'     http://www.dynare.org/sebastien
  `-      GPG Key: 4096R/381A7594
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 835 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-octave-devel/attachments/20120720/3f88ffd3/attachment.pgp>