(1) Add a "rm -f ${PREFIX}/bin/inews", install was failing when it tried
to overwrite an inews installed by a separate package (it su's first).
(2) Add "-c" to install lines of manpages.
changing quite rapidly according to Peter. If someone is willing to
maintain it, go ahead and upgrade.
By the way, this is the 300th port. Congratulations Peter, you get
any ten of the 300 ports for free! :)
Submitted by: Peter Wemm <peter@haywire.DIALix.COM>
/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.
ftp://ftp.freebsd.org/pub/FreeBSD/distfiles/
as our distribution point for distfiles and patches. Other than
cosmetic changes (freebsd.cdrom.com -> ftp.freebsd.org), the
omission of "ports" is important. I would like to move this
directory completely out of the ports tree (on the ftp site),
so that people who do "get ports.tar.gz" won't get a bogus distfiles
-> ../distfiles symlink (which will make "make fetch" fail).
Sometime around the 2.1 release, the distfiles link will be deleted.
set permissions and ownerships of PREFIX (usually /usr/local). This
is the default if USE_IMAKE or USE_X11 is set.
This should be useful for machines like thud, where we want to keep
the /usr/local subtree writable to a group ("ports" in our case). Anybody
who installs stuff in /usr/local should have this set in the environment.
Note this won't affect anything the pkg_* suite does.
post-install:
pkg_add -m ${PREFIX}/lib
to Makefiles and
@exec ldconfig -m %D
to packing lists of ports that install shared libraries.
This should get rid of a huge chunk of confusion for novice users!
All hail Paul Kranenburg! :)
Note that the two "touch"s I took out from do-patch shouldn't have
been there in the first place.
This target may give incorrent results if two separate patches deal
with the same file, and their hunks overlap. (But having those kinds
of patches are bad, and they should be merged anyway.)
Reviewed by: hsu
