Bug 196300 - [MAINTAINER] print/fontforge: Update to 20141126
Summary: [MAINTAINER] print/fontforge: Update to 20141126
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Only Me
Assignee: freebsd-ports-bugs (Nobody)
URL:
Keywords: needs-qa, patch, patch-ready
Depends on:
Blocks:
 
Reported: 2014-12-27 16:42 UTC by Naram Qashat
Modified: 2015-01-04 15:54 UTC (History)
1 user (show)

See Also:


Attachments
fontforge-20141126.patch (57.01 KB, patch)
2014-12-27 16:42 UTC, Naram Qashat
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Naram Qashat 2014-12-27 16:42:11 UTC
Created attachment 150992 [details]
fontforge-20141126.patch

This is quite a major update of this port. Some key notes:

* Development (and thus distfile) moved from SF to GitHub.
* Some libraries were made unconditional (like freetype and pango) because fontforge has no configure options to disable them and will use them if they exist, so this is to prevent issues when those libraries are updated.
* Utilized PORTDOCS instead of listing in them in the pkg-plist.
* A lot of the options were removed due to the above note about fontforge's configure not having options to disable some things.
* Python support in fontforge appears to work on both i386 and amd64 now.
* Docs are now included in the main tarball, so the separate logic was removed for that.
* fontforge has a bootstrap script that comes with it, in other to do things like autoreconf, but the script fails if the user doesn't have git installed, DESPITE the bootstrap script having a --skip-git argument. As such, I have added a pre-configure target to do the relevant commands from that bootstrap. Because of this, I needed access to libtoolize and autoreconf without allowing the ports system to run them automatically. (If there is a way to still allow the ports system to run autoreconf but make autoreconf not run libtoolize, I could remove that from the pre-configure target, but until then, this is how it needs to be done.)
* All previous patches were invalid for the new fontforge, and new patches are in place for the new fontforge.

Here are some relevant poudriere logs:

http://kirby.cyberbotx.com/poudriere_logs/fontforge-20141126-9amd64.log
http://kirby.cyberbotx.com/poudriere_logs/fontforge-20141126-9i386.log
http://kirby.cyberbotx.com/poudriere_logs/fontforge-20141126-10amd64.log
http://kirby.cyberbotx.com/poudriere_logs/fontforge-20141126-10i386.log
Comment 1 commit-hook freebsd_committer 2015-01-04 15:49:07 UTC
A commit references this bug:

Author: riggs
Date: Sun Jan  4 15:48:28 UTC 2015
New revision: 376240
URL: https://svnweb.freebsd.org/changeset/ports/376240

Log:
  - Update to upstream version 20141126
  - Remove OPTIONS MULTILAYER, PLUGINS and PANGO
  - Simplify Makefile

  PR:		196300
  Submitted by:	cyberbotx@cyberbotx.com (maintainer)

Changes:
  head/print/fontforge/Makefile
  head/print/fontforge/distinfo
  head/print/fontforge/files/patch-Makefile.am
  head/print/fontforge/files/patch-Makefile.dynamic.in
  head/print/fontforge/files/patch-configure
  head/print/fontforge/files/patch-configure.ac
  head/print/fontforge/files/patch-fontforge_Makefile.dynamic.in
  head/print/fontforge/files/patch-fontforge_cvexport.c
  head/print/fontforge/files/patch-fontforge_print.c
  head/print/fontforge/files/patch-fontforge_splineutil2.c
  head/print/fontforge/files/patch-mk_layout.am
  head/print/fontforge/files/patch-plugins-Makefile.in
  head/print/fontforge/pkg-plist
Comment 2 Thomas Zander freebsd_committer 2015-01-04 15:54:38 UTC
I could not test this on 8.4 because libspiro does not build there. Could you have a look at it?