/usr/local/share/emacs/site-lisp
/usr/local/lib/mule-site-lisp
as the "site-lisp" directories. Basically all I did was tuck
--locallisppath=${PREFIX}/share/emacs/site-lisp:${PREFIX}/lib/mule/site-lisp
to the end of CONFIGURE_ARGS.
Also, all the patch-aa's are unnecessary because bsd.port.mk now will
take ${CFLAGS} from /etc/make.conf and put it in the environment before
calling configure.
Unfortunately, the copyright is somewhat restrictive, so we cannot
make a package out of it. The author seem no longer to be reachable
under the provided mail address.
=====
# Id line
#
# RESTRICTED: restricted_port_1 (comment1)
# RESTRICTED: restricted_port_2 (comment2)
#
# BROKEN: broken_port_3 (comment3)
# BROKEN: broken_port_4 (comment4)
# BROKEN: broken_port_5 (comment5)
#
SUBDIR= good_port_1 good_port_2 ...
=====
Basically, the idea is to make it easy to find restricted or broken
ports by doing a "grep".
split mule into three ports:
editors/mule: no language-specific support
japanese/mule-canna: Japanese support, Canna library built-in
japanese/mule-wnn: Japanese support, Wnn library built-in
Note that the two ports under japanese/ will overwrite some of the
emacs support files. Although this itself isn't a problem, if you
pkg_delete it, you will lose some files needed for emacs. (This is
explained in DESCR, although god knows who reads them.)
Also I've listed every single file in the PLIST.
Note: post-build and cannainfo.el are necessary only for reformatting one of
the info files whose source was patched, and can go away when the next
minor release (i.e., 2.3) comes out.
This does no longer exists. The man page are in man/man1. Also some were
missing in the packing lis ( teachjove.1, xjove.1, jovetool.1 ) that are
installed from the make install.
called with a "-s" flag for shell-scripts, fells flat on the nose and doesn't
install them.
We have a serious problem with name overloading here. The bsd.port.mk file
uses INSTALL and INSTALL_PROGRAM that is also used from GNU's autoconfigure
script. If configure detects them it uses it happily with sometimes surprising
results. Normally configure know that shell scripts doesn't need the "-s"
flag but our INSTALL in bsd.port.mk always uses the "-s" flag and overides
configure's autodetection of the correct install and the installflags.
