[Pkg-fonts-devel] Bug#651600: Bug#651600: Claiming this package

[Vasudev Kamath]

On 10:29 Thu 15 Nov     , Fabian Greffrath wrote:
> Am 14.11.2012 17:57, schrieb Vasudev Kamath:
> >I think that is not correct because fonts-droid comes from
> >droidfonts.com [1] and Roboto is not listed there. Roboto can be
> >downloaded from here [2]
> 
> Sorry, but I am afraid this is also wrong. These may be the sites on
> which the fonts were initially announced. But it's surely not where
> they are developed and maintained. AFAICT, you cannot even download
> the Droid fonts from the site you mentioned.
> 
> For the Debian package, the fonts are prepared from a GIT checkout, see:
> <http://anonscm.debian.org/viewvc/pkg-fonts/packages/fonts-droid/trunk/debian/README.Debian?view=markup>

I see I didn't knew about these site I saw the link from RFP.

> 
> The advantage is that the fonts are taken directly from the place
> where they are developed, where Google actually takes them from for
> their Android releases and wherey they are automatically versioned
> by means of GIT release tags. Moreover, this issue has been
> discussed in Fedora before and it turns out that the GIT repository
> is indeed the canonical source for Droid, see (I'd recommend to read
> through the other posts of this thread as well, though they are a
> bit scattered through the list archive):
> <http://lists.fedoraproject.org/pipermail/devel/2012-July/169838.html>

I see thanks for this link.

> 
> If you check out that specific directory in the Android source
> repository that is mentioned in the README.Debian file, you will see
> that the Roboto fonts are also there:
> <https://android.googlesource.com/platform/frameworks/base/+/HEAD/data/fonts/>
> 
> It is just that they are currently stripped from the Debian package
> source tarball, see README.Debian.

Yes looks like maintainer of the fonts-droid wants it to be in separate
package.

> 
> So, what I suggests is to change the Debian source package name to
> "fonts-android", check out the complete sources from the data/fonts
> directory in the Android GIT repository based on a specific release
> tag (e.g. android-4.1.2_r1) and set the source package version to
> that tag (e.g. 4.1.2.r1), build two binary packages "fonts-droid"
> and "fonts-roboto" from this source package. This is close to how
> Fedora does it, but they are currently restricting the fonts to the
> Droid* ones by means of a GIT sparse-checkout, see:
> <http://pkgs.fedoraproject.org/cgit/google-droid-fonts.git/tree/getdroid.sh>

Idea is good but again it depends on what does the maintainer of
fonts-droid thinks about this because this change requires changes to
his package. So what do you suggest write to him separately or is he
subscribed here?

Regards
-- 
Vasudev Kamath
http://copyninja.info
Connect on ~friendica: copyninja@{frndk.de | vasudev.homelinux.net}
IRC nick: copyninja | vasudev {irc.oftc.net | irc.freenode.net}
GPG Key: C517 C25D E408 759D 98A4  C96B 6C8F 74AE 8770 0B7E
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-fonts-devel/attachments/20121115/ddb5c8e5/attachment.pgp>