Am Samstag, den 31.01.2009, 09:43 +0100 schrieb Nicolas Mailhot:
Le vendredi 30 janvier 2009 à 20:28 -0300, Paul Lange a écrit :
> Hey,
> thank you for your fast answer!
np
> I created a Review request for my package. You find it here:
>
https://bugzilla.redhat.com/show_bug.cgi?id=483363
I'll look at it soonish.
For actual sponsoring I'll wait for one or two more successful
submissions by you, as the fonts packaging process has been streamlined
so much a single submission is not really selective nowadays.
Thank you for looking at it. I improved both summary and description a
bit - so it's (more or less) perfect now ;)
> One thing I noticed when going through the Joining the Fonts
SIG
> wikipage: There is written that you should apply for membership in the
> cvsextras group on fas. This group does (not longer) exist.
Thank you for noticing *and reporting* this. Should be fixed now (BTW
anyone declared in FAS is free and encouraged to fix and improve the SIG
wiki pages, only the official guidelines are locked)
That's clear but I didn't know how the group is called now.
> One more question. I started looking at the next font -
Vollkorn.
>
http://www.grafikfritze.de/?p=43
>
> On the website there is only the *.otf file. Should I put it into an
> archive for packaging?
Try to always use the files in the form provided upstream with their
exact link in Source: . The only exceptions are archives that include
stuff we can not distribute, even in an srpm, or archives that need a
non-free unpacker. In those cases we do re-create source archives but
it's and exception mode that should be avoided as much as possible.
Well, created an archive for it. Now my next question is how to handle
this in the spec-file:
#URL of the font, not the download
URL:
http://www.grafikfritze.de/?p=43
#Path to the archive I created
Source0: %{archivename}.tar.gz
#Path to the fontconf file
Source1: %{name}-fontconfig.conf
Should I create a Source2 field with the URL of the download or
introduce a URL2 field?
Thanks!
Paul