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 archs supported by emulator (use as last resort) > 4) cross-compile arch (don't install binaries from there, only libs) > 1-3 is just a matter of preference, affect only apt and can be > configured using pining. But for 4 the Packages file needs to be > filtered and dpkg should require extra force to install a binary package > for that arch. I disagree that there's anything special about the cross-compile case. This is just another level of preference; packages for the cross-compile arch should be pulled in only when explicitly requested, which in the context of build-dependencies they obviously will be. There's no need to complicate the configuration interface, pinning handles this as well as it does the other cases. If you actually wind up pulling in binaries in the process, <shrug> - the package has broken build-dependencies. Fix that - don't overengineer the preferences interface declaration. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer http://www.debian.org/ slanga...@ubuntu.com vor...@debian.org
signature.asc
Description: Digital signature
