Steve Langasek vor...@debian.org writes:
On Wed, Feb 16, 2011 at 04:30:31PM +0100, Goswin von Brederlow wrote:
This needs some redesign I'm afraid. Specifically in combination with
cross-compiling.
There are 4 kinds of architectures:
1) the native arch (the prefered arch)
2) foreign archs
Steve Langasek vor...@debian.org writes:
Package: apt
Version: 0.8.11.1
Severity: important
Hi there,
Currently, apt's support for multiarch requires users to manually set
APT::Architectures in apt.conf to tell apt which architectures are allowed.
But dpkg also needs to know what
On Wed, Feb 16, 2011 at 04:30:31PM +0100, Goswin von Brederlow wrote:
This needs some redesign I'm afraid. Specifically in combination with
cross-compiling.
There are 4 kinds of architectures:
1) the native arch (the prefered arch)
2) foreign archs directly supported by the cpu
3) foreign
On Fri, Feb 11, 2011 at 22:39, Steve Langasek vor...@debian.org wrote:
Since 'dpkg -i' and 'apt-get install' should both have the same view of the
world, I think apt should be pulling this information from dpkg - which it
can do with 'dpkg --print-foreign-architectures'. (This command will
On Tue, Feb 15, 2011 at 10:19:40PM +0100, David Kalnischkies wrote:
On Fri, Feb 11, 2011 at 22:39, Steve Langasek vor...@debian.org wrote:
Since 'dpkg -i' and 'apt-get install' should both have the same view of the
world, I think apt should be pulling this information from dpkg - which it
Package: apt
Version: 0.8.11.1
Severity: important
Hi there,
Currently, apt's support for multiarch requires users to manually set
APT::Architectures in apt.conf to tell apt which architectures are allowed.
But dpkg also needs to know what architectures are allowed, and the
in-progress multiarch
6 matches
Mail list logo