Hi Thomas, Quoting Thomas Goirand (2015-09-07 19:53:16) > On 09/07/2015 07:00 PM, Vasudev Kamath wrote: >> We already have a fonts-roboto which is part of fonts-android >> source. ¹. There was a discussion on pkg-fonts-devel IIRC previously to >> split roboto fonts to its own package as code was moved to its own git >> repository. Sorry but I don't exactly have the link to discussion, so >> ccing fonts team. >> >> I wonder if we can eliminate duplicate and have a single font. >> >> ¹ https://packages.debian.org/unstable/fonts-roboto
> That's not the same package. The one that I'm packaging has not only > the .ttf files, but also .eot, .svg, .woff and .woff2, plus .css, > .less and .scss files. All of these are needed for the web developers. Seems the project you want to package only includes the Roboto font, but is not the canonical source of the font: Package description begins with "A simple package providing the Roboto fontface." > If you wish to drop the generation of fonts-roboto from the > fonts-android package, then good. I think the better approach is to keep the fonts-roboto package, have your package exclude fonts, depend on the fonts-roboto package, and symlink font files from there as needed. > Do you think I should join the pkg-fonts group to maintain these fonts > under the group? We can always use more helping hands in the fonts team :-) But if your focus is on OpenStack then perhaps just coordinate with the font team on tuning the fonts-roboto package to provide what is needed for reuse with OpenStack - i.e. those web representations of the font (CSS/Sass/Less sounds like OpenStack-specific glue so probably makes best sense to package separately). Kind regards, - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private
signature.asc
Description: signature
