On Fri, Feb 06, 2009 at 11:15:43AM +0100, Frans Pop wrote: >On Thursday 05 February 2009, Frans Pop wrote: > >So the following really has to be implemented in update_tasks itself. > >On Thursday 05 February 2009, Frans Pop wrote: >> So IMO: >> * ideally we should run update_tasks for every architecture separately, >> using the Packages file for that arch; for source-only CDs we should >> use i386 with fallback to amd64, and fail otherwise >> * but as long as we do not do that >> - for binary or binary/source CDs: prefer i386, with fallback to: >> 1) amd64 >> 2) arches listed in $ARCHES >> - for source-only CDs: use i386, with fallback to amd64, and fail >> otherwise > >But, given the reasons I gave in [1], we could also do this a bit >differently and as a bonus improve the task expansion: > >* if ARCHES contains a single arch OR a single arch + "source", then > use that arch >* if ARCHES contains multiple arches or is source-only, then use i386 > with a fallback to the arches listed in ARCHES
In fact, I'd say the simplest answer would be to pick the first named arch. If we're doing source-only then don't run update_tasks at all. How does that sound? -- Steve McIntyre, Cambridge, UK. st...@einval.com "Because heaters aren't purple!" -- Catherine Pitt -- To UNSUBSCRIBE, email to debian-cd-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org