[Bug 239768] print/fontforge: Update to 20190801

[bugzilla-noreply at freebsd.org]

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

Naram Qashat <cyberbotx at cyberbotx.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
              Flags|maintainer-feedback?(cyberb |maintainer-feedback+
                   |otx at cyberbotx.com)          |

--- Comment #2 from Naram Qashat <cyberbotx at cyberbotx.com> ---
So I'm finally getting around to looking into this and it'll take me some time.
They moved from autotools to CMake for their build system as well.

I'm also wondering if I should make more things optional in the port instead of
forcing them as is currently being done. Examples of what could be optional
now:

* libspiro
* libuninameslist (as described by koobs)
* giflib
* jpeg
* png
* readline
* tiff

Also the 'tile path' command (formerly using the --enable-tile-path flag to
configure) could be optional instead of forced.

The GUI toolkit can be chosen between either a GTK3-based one or one that uses
plain X11 (or even disabling it which I think would only give command-line
tools).

Making cairo optional seems to no longer be a thing (only required by fontforge
itself when not using GTK3).

There's an option for Fontforge's native scripting, not sure if that should be
an option in the port.

The changes are listed here:

https://github.com/fontforge/fontforge/wiki/CMake-guide-for-FontForge

And for reference, the previous version's configure.ac:

https://github.com/fontforge/fontforge/blob/20190413/configure.ac

So before going forward, I'd like advice on how to proceed with such a big
change. Most likely to keep the port's packaging somewhat consistent, I'd set
the above points as default options.

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