literal name_enable wherever possible, and ${name}_enable
when it's not, to prepare for the demise of set_rcvar().
In cases where I had to hand-edit unusual instances also
modify formatting slightly to be more uniform (and in
some cases, correct). This includes adding some $FreeBSD$
tags, and most importantly moving rcvar= to right after
name= so it's clear that one is derived from the other.
propogated by copy and paste.
1. Primarily the "empty variable" default assignment, which is mostly
${name}_flags="", but fix a few others as well.
2. Where they are not already documented, add the existence of the _flags
(or other deleted empties) option to the comments, and in some cases add
comments from scratch.
3. Replace things that look like:
prefix=%%PREFIX%%
command=${prefix}/sbin/foo
to just use %%PREFIX%%. In many cases the $prefix variable is only used
once, and in some cases it is not used at all.
4. In a few cases remove ${name}_flags from command_args
5. Remove a long-stale comment about putting the port's rc.d script in
/etc/rc.d (which is no longer necessary).
No PORTREVISION bumps because all of these changes are noops.
- Chase libclamav version bump on all dependant ports
- Bump necessary PORTREVISIONS
- Fix some BROKEN messages from ports that were already broken with clamav-0.93
- Mark security/klamav as BROKEN since it doesn't build with clamav-0.94
PR: ports/127122 [1], ports/127310 [2]
Submitted by: Gary Palmer <freebsd-gnats@in-addr.com> [1], delphij [2]
Approved by: portmgr (pav)
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)
- Bump PORTREVISION
Following ports are marked as BROKEN since they don't build with new clamav
0.93:
www/c-icap
mail/claws-mail-clamav
www/gurlchecker
www/havp
security/klamav
devel/p5-Mail-ClamAV
devel/py-clamav
www/squidclam
This clamav version needed to be updated without wait other ports fixes
because it fixes important vulnerabilities.
- Add a new OPTION (RAR) because unrar code is optional to fix a license
issue
- Some cosmetic changes
- Chase library version bump and bump PORTREVISION of all dependant ports
Approved by: portmgr (pav)
Security: CVE-2007-6335, CVE-2007-6336, CVE-2007-6337
Something in the infrastructure changed in the late July timeframe that
actually caused this problem. The only major thing at that time was the
autoconf/libtool change, but I can't see how that could have caused this
failure mode. It only happens on 5.x; 6.x and 7.x are fine.
Approved by: portmgr (self)
- Use -lthr to build clamav since it has problems with libpthread
- Bump PORTREVISION of dependant ports, libclamav version was bumped
- Fix clamcour to build with clamav-0.90.x using patch sent by maintainer
- Marked as BROKEN on 4.x (compile problem reported to author)
- Added CONFIGURE_TARGET in Makefile
PR: 101300
Submitted by: Elisey Savateev (maintainer)
main aims are continuous, non-blocking downloads and smooth scanning of
dynamic and password protected HTTP traffic. Havp antivirus proxy has a parent
and transparent proxy mode. It can be used with squid or standalone.
WWW: http://www.server-side.de/
PR: ports/99073
Submitted by: Elisey Savateev <b3k@mail.ru>
