On Thu, 2011-02-17 at 12:57 -0400, Joey Hess wrote: > Adam D. Barratt wrote: > > In order to ensure that packages marked as "key" for a task remain present > > and installable in testing, britney uses a generated "faux" package which > > depends on each of the packages. [...] > > We've therefore been looking at splitting the single faux package in to a > > set of faux packages, one per task. [...] > Before you spend too much time on that, I have been thinking about > converting tasksel's tasks back to real packages. Now that recommends > are installed by default, it should be possible to make tasks use > Recommends for normal contents, and Depends for Key components.
Time passed, and a version of tasksel which implements the "real package" approach will migrate to testing in the next day or so. joeyh / -boot - could you confirm that the task overrides {can,should} be dropped (and thus the fields removed from the Packages files for testing) once the current version of tasksel migrates? >From the britney point-of-view, I'm looking at dropping most of the current tasksel-meta-faux-* generation in favour of a single faux package which depends on all of the real task-* packages. This would allow us to track co-installability of the tasks. I also think we should move the tasksel-specific functionality in to the main "generate" section, as we can simply ask dak for the list of binaries. Comments / queries / whatever? Adam -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1312568931.31497.10.ca...@hathi.jungle.funky-badger.org