Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 18 Aug 2019 20:49:54 +0000
From:      bugzilla-noreply@freebsd.org
To:        ports-bugs@FreeBSD.org
Subject:   [Bug 239768] print/fontforge: Update to 20190801
Message-ID:  <bug-239768-7788-IsKKotpJw6@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-239768-7788@https.bugs.freebsd.org/bugzilla/>
References:  <bug-239768-7788@https.bugs.freebsd.org/bugzilla/>

next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D239768

Naram Qashat <cyberbotx@cyberbotx.com> changed:

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

--- Comment #2 from Naram Qashat <cyberbotx@cyberbotx.com> ---
So I'm finally getting around to looking into this and it'll take me some t=
ime.
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 instea=
d 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 u=
ses
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 fontf=
orge
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 s=
et
the above points as default options.

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



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-239768-7788-IsKKotpJw6>