[Pkg-fonts-devel] Updated fonts-android has fonts missing

Vasudev Kamath vasudev at copyninja.info
Mon Oct 12 17:13:27 UTC 2015

Jonas Smedegaard <dr at jones.dk> writes:

>>> It is meaningful to package fallback DroidSans fonts: It has reverse 
>>> dependencies! But it sure makes sense to check if current upstream is 
>>> bogus - i.e. if development has moved somewhere else.
>> Hmm but logs in their repository talks a lot about merge in notofonts 
>> I didn't observe carefully though.
>> If it makes sense to package only fallback fonts it can be done but we 
>> also need to check latest noto sources to see if it has Droid series 
>> merged then we probably need to provide some sort of movement from 
>> fonts-droid to newer upstream.
>> We need to drop fonts-roboto also and there is no alternative as long 
>> as we get all build tools and fontforge in proper shape or else we 
>> need to provide prebuilt ttf/otf files but I guess that is no longer 
>> recommended right?
> That's multiple questions, some more complex to handle than others.
> If you raise those questions together, the discussion risk being 
> confusing and drag out.

Thats true but I just mentioned all questions which arrise due to the
changes in upstream :-). We can take them one at a time but all of them
are related.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 818 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-fonts-devel/attachments/20151012/b32b6050/attachment.sig>

More information about the Pkg-fonts-devel mailing list