[Pkg-fonts-devel] Please adopt the pkg-fonts team's package naming convention

[Fabian Greffrath]

Package: tex-gyre,lmodern
Severity: wishlist

Hi,

again, the subject line already tells it all. The pkg-fonts team's 
package naming convention currently looks like

  fonts-[$(foundry)-]$(family)

where the $(foundry) part is optional (but would be "gust" in both 
cases, I guess).

There are two things to keep in mind that are particular for the two 
packages in question:

1) The tex-gyre package name already contains a minus '-'.
I don't think we have a strict rule for this, but for the 
"fonts-linuxlibertine" package we simply removed the minus from the 
font family name in order to avoid confusion about "linux" being a 
foundry.

2) Should you follow my requests from #689575 and #689580, there would 
be two packages from the same source shipping the same fonts in 
different formats. While this should be avoided whenever possible, I 
don't think we have a strict rule about dealing with the font packages 
names when this is necessary (and it definitely *is* in this case). 
For the GNU Freefont we thus introduced a "fonts-freefont-otf" and a 
"fonts-freefont-ttf" package.

Finally, if you decide against splitting the Opentype flavours off 
into separate packages we would end up with

  fonts-texgyre

and

  fonts-lmodern

But if you decide to introduce separate packages for the Opentype 
flavours, we would have to distinguish the packages from each other. 
I'd suggest

  fonts-{lmodern,texgyre}-otf

or simply

  fonts-{lmodern,texgyre}

and either

  fonts-{lmodern,texgyre}-extra
                     (or -type1 or -tex or -latex or whatever)

or

  texlive-fonts-{lmodern,texgyre}

I'll add the pkg-fonts team in CC for further discussion.

  - Fabian