[Debian-in-workers] [smc-discuss] New g03 version of Rachana and Meera

[Christian Perrier]

Quoting Praveen A (pravi.a at gmail.com):

> Soumyadeep,
> 
>  Now we are maintaining Rachana fonts and MalOtf, so smc is the
> upstream for ttf-malayalam-fonts. New releases comes at
> http://suruma.sarovar.org/deb/fonts/ It also includes new OpenType
> font Meera and suruma. What do you think is the best way to keep the
> packages updated and not duplicate efforts? We might have to go
> through the new package process because 2 new fonts are coming in.
> 
> May be you can continue to own the package but you won't need much
> work maintaining it as upstream itself is releasing the deb package.
> 
> (smc-discuss is members only, so reply all won't work)
> 
> Rajeesh,
> 
> Can you make a spec file that uses this tarball directly? What name
> the rpm should have? I think suruma-fonts-malayalam fits the Fedora
> naming convention with it providing fonts-malayalam like lohit does.
> 
> Ani,
> 
>  We need these fonts to be included in Fedora proper, ball is now in your court.
> 
> Suresh can include all these changes and make a ttf-malayalam-fonts
> and Rachana_04


It is maybe time to think about the status of ttf-indic-fonts in
Debian. Currently, that source package is a collection of various
stuff of different origins.

It makes things hard to gather together and maintain, imho. While it
may make sense for fonts that are loosely maintained, in the case of
Malayalam fonts, where maintenance seems pretty active (identified
upstream repository for instance), it could be a better idea to split
the package out of ttf-indic-fonts and have a maintenance that's as
close of upstream as possible.


-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://lists.alioth.debian.org/pipermail/debian-in-workers/attachments/20080126/51d8ad4a/attachment.pgp