[Pkg-fonts-devel] FontForge Packaging

Frank Trampe frank.trampe at gmail.com
Mon Aug 4 16:58:33 UTC 2014


Hi, Fabian.

I'm indeed working on upstream FontForge.

The current plan is not to include a static debian directory in the source
root (as has happened in the past) so as to make things easier for others
packaging the product differently. I'm adding a deb-src make target that
generates the debian control directory and runs debuild.



On Mon, Aug 4, 2014 at 2:41 AM, Fabian Greffrath <fabian at greffrath.com>
wrote:

> Dear Frank,
>
> Am Dienstag, den 29.07.2014, 18:14 -0500 schrieb Frank Trampe:
> > I'm working to add automatic packaging functionality to FontForge in
> > support of what we hope to be frequent releases in a dedicated package
> > repository (to be created soon). It seems that it would save me a lot
> > of work and do a lot to maintain compatibility if I were to borrow
> > most of the metadata from the existing Debian packaging overlay. Does
> > this seem to be a reasonable approach?
>
> I am not sure if I understand your approach correctly.
>
> 1) Are you upstream for fontforge?
> 2) Are you telling that you are going to add a debian/ subdirectory to
> fontforge release tarballs?
>
> Cheers,
>
> Fabian
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/pkg-fonts-devel/attachments/20140804/a19ac799/attachment.html>


More information about the Pkg-fonts-devel mailing list