On Tue, Oct 23, 2007 at 08:03:01PM -0400, Joey Hess wrote: > dann frazier wrote: > > I want to use the udeb in the primary suite if there is no > > corresponding udeb in the override_suite. The override_suite only > > includes udebs that require customization. Does that answer your > > question? > > No, because I don't see how it works. Like I said, it downloads the > Release and Packages files for the primary suite. Then it downloads > those from the override suite, over top of them. Only the override suite > Packages info is left, so how is d-i supposed to know how to find udebs > from the primary suite?
To be honest I added this back on top of sarge and had to reread the code to remember how it worked :) The Packages file isn't being overwritten; its being appended to. The existing version concatenates the Packages file for each component in a single suite - presumably to allow for things like 'etch non-free/debian-installer' This patch makes it so the components from the override suite are included as well. When searching for a udeb in the Packages file, I don't recall if its the first match that wins or the greatest version, but either way the binaries in the override suite take precedence since: * The contents of the override suite's Packages file are always at the of the generated Packages files * I ensure the override packages always have a greater version :) Of course, this could probably be extended to allow for an arbitrary number of suites (one primary and one override feels like a 0:1:infinity violation). -- dann frazier -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]