Bug#291939: Split System/Cpu for architecture handling
On Mon, Jan 24, 2005 at 01:05:28PM +0000, Scott James Remnant wrote:
> >
> > As I just said to Goswin, my patch doesn't modify the way dpkg handles
> > architectures internaly. dpkg-genchanges uses Cpu/System logic to determine
> > wether we can build a package, but when generating DEBIAN/control it will add
> > an "Architecture" field set to DEB_HOST_ARCH.
> >
> More accurately, dpkg-genchanges determines what we probably just built;
> it's not used to decide what to build, and what not to build, your rules
> file has to do that.
Oh, I'm sorry. I meant to say dpkg-gencontrol here. :)
> So your changes don't remove "Architecture: all"? How would somebody
> express anything? "Architecture: any" still?
Cpu: all / System: all == Architecture: all
Cpu: any / System: any == Architecture: any
Mixed any/all settings are syntacticaly supported, although since dpkg or DAK
wouldn't support them, Cpu is mandatory for now:
Cpu: any / System: all == Architecture: any
(e.g. a package with pure-i386 executables like GRUB stage files)
Cpu: all / System: any == Architecture: all
(e.g. kernel sources or system-specific documentation)
In the future DAK/dpkg should be able to understand these combinations, though.
> What about (e.g.) dpkg-checkbuilddeps and dpkg-gencontrol ?
My changes to controllib.pl affect dpkg-checkbuilddeps' parsing of
Build-Depends the way I described before.
--
.''`. Proudly running Debian GNU/kFreeBSD unstable/unreleased (on UFS2+S)
: :' :
`. `' http://www.debian.org/ports/kfreebsd-gnu
`-
Reply to: