[EMAIL PROTECTED] writes:
> There should be a virtual package for mp3-decoder which includes packages
> such as
Do you have a reason? Do you want to add a dependency on
"mp3-decoder" to one of your packages? I'd like to keep the virtual
package list fairly minimal for now, and not add things unless they're
required. (Or at least "Suggest:"ed :-).
Justify the proposal and I'll gladly agree.
Two things I'd like to see done with the virtual package system:
1. Define APIs for all virtual packages.
2. Tie virtual packages to the alternatives system, somehow.
The former emphasises the fact that, unless you have *some* sort of
common API (no matter how fuzzy), you don't really have a virtual
package. The latter may be pie-in-the-sky, but could be interesting.
Anyway, you don't need to make a formal policy proposal to add/change
virtual packages or the menu tree. Those are stored separately for
just this reason, and merely require discussion on the d-policy list.
--
Chris Waters [EMAIL PROTECTED] | I have a truly elegant proof of the
or [EMAIL PROTECTED] | above, but it is too long to fit into
http://www.dsp.net/xtifr | this .signature file.
