I've recently found out that I need fontforge and the python bindings for creating fonts (ForkAwesome) but the package on MacPorts is really, really old.
The project has moved from sourceforge to github and I was trying to create a new Portfile (since it doesn't have a maintainer), but I ran into a few issues: The packages are available on github (https://github.com/fontforge/fontforge/releases) but the names of the dist tarballs do not conform to any convention. e.g.: https://github.com/fontforge/fontforge/releases/download/20161005/fontforge-dist-20161004.tar.gz https://github.com/fontforge/fontforge/releases/download/20170731/fontforge-dist-20170731.tar.xz So release 20161005 uses fontforge-dist-20161004.tar.gz and release 20170731 uses fontforge-dist-20170731.tar.xz Not even sure, if it's even possible to solve this unless there's a way to hardcode the download address (which I also do not know how to do). Hmm, so maybe building from git master. Well, the package doesn't use ./autogen.sh but some other script called bootstrap. So how do I run bootstrap instead of autogen.sh? Do I just use: use_autoreconf yes autoreconf.cmd ./bootstrap In any case, I could need some help with the Portfile. While it looks like a dependecy hell at first sight (current Portfile), I believe it is not as bad as it looks. I don't think the patches are required anymore, and the current build process should be rather straight forward. For a MacPorts Portfile expert, this should be a matter of a few minutes, so if you can spare a few of those, please help me. Cheers, K. C. -- regards Helmut K. C. Tessarek KeyID 0x172380A011EF4944 Key fingerprint = 8A55 70C1 BD85 D34E ADBC 386C 1723 80A0 11EF 4944 /* Thou shalt not follow the NULL pointer for chaos and madness await thee at its end. */
signature.asc
Description: OpenPGP digital signature
