Specifically, newer autoconf (> 2.13) has different semantic of the
configure target. In short, one should use --build=CONFIGURE_TARGET
instead of CONFIGURE_TARGET directly. Otherwise, you will get a warning
and the old semantic may be removed in later autoconf releases.
To workaround this issue, many ports hack the CONFIGURE_TARGET variable
so that it contains the ``--build='' prefix.
To solve this issue, under the fact that some ports still have
configure script generated by the old autoconf, we use runtime detection
in the do-configure target so that the proper argument can be used.
Changes to Mk/*:
- Add runtime detection magic in bsd.port.mk
- Remove CONFIGURE_TARGET hack in various bsd.*.mk
- USE_GNOME=gnometarget is now an no-op
Changes to individual ports, other than removing the CONFIGURE_TARGET hack:
= pkg-plist changed (due to the ugly CONFIGURE_TARGET prefix in * executables)
- comms/gnuradio
- science/abinit
- science/elmer-fem
- science/elmer-matc
- science/elmer-meshgen2d
- science/elmerfront
- science/elmerpost
= use x86_64 as ARCH
- devel/g-wrap
= other changes
- print/magicfilter
GNU_CONFIGURE -> HAS_CONFIGURE since it's not generated by autoconf
Total # of ports modified: 1,027
Total # of ports affected: ~7,000 (set GNU_CONFIGURE to yes)
PR: 126524 (obsoletes 52917)
Submitted by: rafan
Tested on: two pointyhat 7-amd64 exp runs (by pav)
Approved by: portmgr (pav)
* Put deprecation warnings in more places in the docs, and in
the podtohtml script
* Use Pod::Simple::HTML instead of this module
Submitted by: delphij
PR: ports/126690
help outside the module system, in pure .html files. The files can
be easily translated simply by copying them into the right translations
directory. The entire system can appear in a popup or not as the
module prefers (and by taking away access to view the popups, a
site can force the popups to not exist).
The system ties into Drupal's search system and is fully indexed,
so the entire contents can be searched for keywords. the help files
can be placed in a hierarchy as well, allowing for top down navigation
of the help.
WWW: http://drupal.org/project/advanced_help
PR: ports/125798
Submitted by: Eygene Ryabinkin <rea-fbsd at codelabs.ru>
<ChangeLog>
*) Change: now ngx_http_charset_module does not work by default with
text/css MIME type.
*) Feature: now nginx returns the 405 status code for POST method
requesting a static file only if the file exists.
*) Feature: the "proxy_ssl_session_reuse" directive.
*) Bugfix: a "proxy_pass" directive without URI part might use original
request after the "X-Accel-Redirect" redirection was used;
*) Bugfix: if a directory has search only rights and the first index
file was absent, then nginx returned the 500 status code.
*) Bugfix: in inclusive locations; the bugs had appeared in 0.7.1.
</ChangeLog>
of KDE 3.5.9 for FreeBSD. The official KDE 3.5.9 release
notes can be found at:
http://www.kde.org/announcements/announce-3.5.9.php
After the KDE 4.1.0 import the team found time to make
KDE 3.5.9 ready for the Ports tree.
KDE 3.5.9 was released six months ago and 3.5.10 is coming
soon. We are not sure we have time to get 3.5.10 for FreeBSD
7.1/6.4 release, but we would have minimum 3.5.9 for those
people who prefer to stay with KDE3.
Of course Thanks to all Testers.
www/squigguard installs blacklist files to /var/db/squidGuard
and the UID:GID of the installed files is set to nobody:nogroup.
The permission for the files is 0550 or 0660. On the other
hand, www/squid specifies squid:squid as UID:GID.
As a result, squidGuard cannot handle blacklist files so
websites that should not be accessed cannot be filtered.
PR: ports/120923
Submitted by: Jiro Kita <ktj@ktjdragon.com>
Approved by: maintainer timeout
The attached patch updates www/privoxy from 3.0.8
to 3.0.10 (3.0.9 was a beta). The ChangeLog is available
at: http://www.privoxy.org/announce.txt
PR: ports/126607
Submitted by: Fabian Keil <fk@fabiankeil.de>
Apache 2 webserver with OpenID
mod_auth_openid is an authentication module for the Apache
2 webserver. It handles the functions of an OpenID consumer
as specified in the OpenID 2.0 specification.
WWW: http://trac.butterfat.net/public/mod_auth_openid
PR: ports/126218
Submitted by: Sutra Zhou <zhoushuqun@gmail.com>
