Andreas Beckmann <deb...@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
pgpV1yFCh7Sqb.pgp
Description: PGP signature
