Hi Paul, > I think doing this properly would require extending tasksel to > allow support for it, then extending blends-dev to support it. As I am entirely new to tasksel, except for the inevitable use when installing Debian through the installer, I might be missing something here. I always thought tasksel merely were a tool to select special meta-packages. Why does tasksel need support for this Conflicts feature, or, more generally, why does it even need to care at all what dependencies the selected tasks have? When looking at the tasks and packages built by the blends tooling, I also see that the _BLEND_-foo task simply tells tasksel to select the _BLEND_-foo package, and then calls apt-get. I don't see why my meta-package should not just be able to declare a Conflicts, then? So, I'd probably be able to add support for Conflicts and Breaks to blend-gen-control, but I need more hints to figure out what tasksel's involvement is. Cheers, Nik
Attachment:
signature.asc
Description: PGP signature