handling of fonts in the langpack plugin

[Bill Nottingham]

Behdad Esfahbod (behdad at behdad.org) said: 
> On 02/27/2012 11:41 AM, Bill Nottingham wrote:
> > Nicolas Mailhot (nicolas.mailhot at laposte.net) said: 
> >> The main problem I see is that current provides are fully automated, and only
> >> require looking at the font package being created content. What you ask for is
> >> a cross-repo require, so either people would need to fill them in manually
> >> (with the reliability and cruft accumulation of cross-processes) or each font
> >> package would need to depend on every other font package in the repo at build
> >> time to check if it's the priority one for a specific language or not.
> > 
> > How so? I'm wondering about the feasibility of a hardcoded list. Right now,
> > we 'know' which fonts should be the default for non-dejavu languages (at
> > least, we set them up that way in comps), so why not add a quick hardcoded
> > provide for those 10-20 packages and just change that provide if the
> > preferred font infrequently changes?
> 
> So, right now we Provide "font(:lang=fa)" from all fonts supporting that
> language.  Why can't you create a metapackage default-fonts that provides
> "font(default:lang=fa)", etc that would then require the default font for the
> language?

The installation of the default fonts for all supported languages (for
some suitable definition of all) is not really my concern - we have a
'fonts' group for that; we could do what you suggest there, but it's not the
primary usage case.

What I'm concerned with is someone who's installing in Japanese, or wants to
specifically add Japanese support, and wants to pull *just* the default
Japanese fonts - a single metapackage doesn't help here.

Bill