[Bug 196300] New: [MAINTAINER] print/fontforge: Update to 20141126

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=196300

            Bug ID: 196300
           Summary: [MAINTAINER] print/fontforge: Update to 20141126
           Product: Ports Tree
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Some People
          Priority: ---
         Component: Individual Port(s)
          Assignee: freebsd-ports-bugs at FreeBSD.org
          Reporter: cyberbotx at cyberbotx.com

Created attachment 150992
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=150992&action=edit
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

-- 
You are receiving this mail because:
You are the assignee for the bug.