${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. :)
on the -current mailing list and at least partial credit goes
to the following people for this commit:
Joachim Kuebart <joki@kuebart.stuttgart.netsurf.de>
Ollivier Robert <roberto@keltia.freenix.fr>
NOTE: Kerberos support has been temporarily turned off until
someone can make it work.
following problems:
- xterm utmp handling problem.
- exploitable buffer overflows in xterm related to the preeditType,
inputMethod and *Keymap resources.
- fix xterm's mishandling of the -vb command line option.
- fix an invisible cursor problem with xterm.
- exploitable buffer overflows in setuid programs using the Xaw library
which are related to the preeditType and inputMethod resources.
o XDM-AUTHORIZATION-1 is more automated for the non-USA case.
o PST's KerberosIV patches are reinstated for XDM. This is NOT
a full-blown KerberosIV implementation for X - this will
just get you a TGT when you log in - THATS ALL!
o Enable compilation of SecureRPC. The use of SecureRPC at the
moment is frought with danger! I have no idea how safe or
good the implementation is. Enable at your own peril!! (Secure
RPC is only available for those folk using 3.0-Current).
Also allow XF86Setup to use TK-8.0.
OK'ed By: JMZ
also it is not true.
ISO8859-1:GR _always_ searched for pressed 8bit key independently of
locale information, so only ISO8859-1 locales really works.
Remove NO_PACKAGE, because XFree distributed package not have
this fixes.
According to Marc Slemko (marcs@alive.ampr.ab.ca) there are potential
security holes in SuperProbe and it is not going to be setuid in the
next release.
