> I like the idea of ttf-lang-* virtual package as well, because for the > input methods packages I maintain, I always want to Depend/Recommend a > font package that has Chinese/Japanese/whatever language, but I don't > care which one, any one will do. So, a short summary of this discussion could be: We request for the creation of virtual packages named ttf-lang-<langname> so that all font packages that are targeted for the supprot of a given language can add a "Provides" on the relevant virtual package(s). The only drawback here is that virtual packages creation is a process that is quite precisely defined in http://www.debian.org/doc/packaging-manuals/virtual-package-names-list.txt and we would need to request for the creation of *a lot* of virtual packages...:-) If these virtual packages are accepted, then our font packages naming policy would say: Font packages are to be named after the name of the font or font family included in the package and should add a "Provides" field listing the ttf-lang-* packages they provide support for.
Attachment:
signature.asc
Description: Digital signature