${MACHINE_ARCH}--freebsd${OSREL} is now passed to CONFIGURE_ARGS if
GNU_CONFIGURE is defined. Take the target out of CONFIGURE_ARGS of
some ports that added it explicitly; define it as
${MACHINE_ARCH}--freebsd if the port doesn't like the ${OSREL} part;
define it as something else (such as ${MACHINE_ARCH}--freebsdelf if
the port requires that; define it as an empty string if the port
doesn't like it at all.
The last might be a sign that a GNU_CONFIGURE port actually doesn't
use GNU's version of configure at all; but I don't have time to go
look at them all, we'll fix them as time goes on.
At least we've got much fewer "-unknown-"s in the tree as the result. :)
use the terminfo version of tparam() since the termcap version supplies
tgoto() which seriously screws up text display. ncurses-4.1 has both a
termcap and terminfo internal interface and is quicker with the terminfo
one even when it's read a termcap.db file.
(which was about equal to number of FreeBSD installations on Hale Bopp
itself). Seems like I need to just go ahead and commit it so people
can try out and scream!
all the COMMENTs! No package names, no version numbers, no "this is
absolutix-3.1.2" type comments that have zero information contents.
Now, without any bad examples to follow, nobody has an excuse to import
a port with those kind of comments. :)
Phew! 238 ports modified!
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.
1. Make MASTER_SITES entries contain a trailing /. Garrett says that
assuming a '/' seperator between entries in MASTER_SITES and entries
in DISTFILES is a dangerous assumption. This will also be taken
out of bsd.port.mk.
2. General clean-up. Some of these Makefiles were a little grim.
Make sure they're all in sync with the sometimes rapidly changing
bsd.port.mk! :)
3. Some small configuration tweaks to keep them compiling under the
most recent 2.0 - some things seem to have broken along our road
to release.
