Can we use the "metapackages" archive section for awesome?

[geofft]

Noticed this in  http://lists.debian.org/debian-devel/2009/12/msg00570.html:

Ubuntu defines a
special archive section, 'metapackages', which results in special
tagging/handling of the Depends and Recommends of the package so that
they're not autoremoved if the metapackage is removed.  This is implemented
in the high-level package management tools.

In this scenario, with Recommends installed by default (the only sane
model), the vast majority of metapackage dependencies are moved from Depends
to Recommends, so you can remove those Recommends manually without forcing
removal of the metapackage; and you can remove the metapackage without
causing cascading autoremoval of e.g., half your desktop.

Can we take advantage of that for our metapackages?

[geofft]

 tasksel as of 3.00 (now in unstable) is using a "tasks" section. I wonder if it interacts with the "metapackages" section, and if it should.

[geofft]

See also  this debian-devel discussion, inspired by, I kid you not, "we see a plethora of users in #debian who ask questions like: 'Why did apt remove all my system??⸘!!!!one!one!eleven!'". There's discussion of both the metapackages archive section and other things like making the aptitude resolver hate removing metapackages.

[geofft]

 Debian policy 3.9.3.0 now endorses the "metapackages" section.