On Wed, Jun 07, 2006 at 04:40:17AM -0600, Matt Jibson wrote:
> print/ec-fonts-mftraced
> print/fontforge
> print/lilypond
> print/mftrace
> print/t1utils
> textproc/texinfo
In addition to what Steven wrote:
1. Use MODULES=lang/python and (in CONFIGURE_ENV) PYTHON=${MODPY_BIN}.
I've done this for mftrace, but I'd prefer to get all this
building and running before sending diffs.
2. print/lilypond/pkg/PLIST goes nuts with fonts.cache-1 (look at
pkg/PLIST).
3. --disable-documentation? Why? Back in Lilypond-2.4 aera it was the
documentation that triggered lots of bugs, especially in
texinfo.
4. ec-fonts-mftraced: use binaries or build from (MetaFont) source?
I'll reserve the complete next weekend for this ports collection ;-)
Ciao,
Kili