Re: new dependency
On Fri, 7 Jul 2000, Joey Hess wrote:
> J.A. Bezemer wrote:
> > I'd say a Recommend:, as only powerpc needs it and most people will be doing
> > only i386. IIRC policy says "if it doesn't work _at all_ then Depends:, if
> > some (less-used?) _parts_ don't work then Recommends:", but check it anyway.
> > Plus add a note to the description that you need hfsutils for powerpc images
> > (a la "need bin86 only for i386 kernels" in kernel-source)
>
> Note that it's possible to make a control file that sets up a dependancy
> on one architecture only. See the task-x-window-system source. In the
> control file, it has:
>
> Depends: ${F:X-${Arch}-Depends} task-x-window-system-core, rstart, [etc]
>
> Then it sets up a debian/substvars like this:
>
> F:X-alpha-Depends=xf86setup, xserver-vga16,
> F:X-arm-Depends=
> F:X-i386-Depends=xf86setup, xserver-vga16,
> F:X-m68k-Depends=
> F:X-powerpc-Depends=
> F:X-sparc-Depends=
That's quite nice, only it's not needed here. The point is that you can build
images for any arch on any (possibly other) arch. Compare a "universal
cross-compiler" ;-) So on both i386 and powerpc you need hfsutils if you want
to build powerpc images, while on both arches you do _not_ need hfsutils if
you want to build i386 images.
(BTW, the same used to hold for lha and m68k images, wasn't it? How were
things handled then?)
Regards,
Anne Bezemer
Reply to: