aboutsummaryrefslogtreecommitdiff
path: root/mail/rabl_client
Commit message (Collapse)AuthorAgeFilesLines
* Update CONFIGURE_ARGS for how we pass CONFIGURE_TARGET to configure script.Rong-En Fan2008-08-211-1/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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) Notes: svn path=/head/; revision=218938
* Switch backup mirror on my other serverIon-Mihai Tetcu2006-06-291-1/+1
| | | | Notes: svn path=/head/; revision=166594
* - s/INSTALL_SHLIB/USE_LDCONFIG/Ion-Mihai Tetcu2006-06-291-2/+2
| | | | | | | - use my @FreeBSD.org address Notes: svn path=/head/; revision=166593
* Conversion to a single libtool environment.Ade Lovett2006-02-231-1/+0
| | | | | | | Approved by: portmgr (kris) Notes: svn path=/head/; revision=156749
* SHA256ifyEdwin Groothuis2006-01-221-0/+1
| | | | | | | Approved by: krion@ Notes: svn path=/head/; revision=154158
* Mass-conversion to the USE_AUTOTOOLS New World Order. The code presentAde Lovett2005-11-151-1/+1
| | | | | | | | | | | | | | | | | | | | in bsd.autotools.mk essentially makes this a no-op given that all the old variables set a USE_AUTOTOOLS_COMPAT variable, which is parsed in exactly the same way as USE_AUTOTOOLS itself. Moreover, USE_AUTOTOOLS has already been extensively tested by the GNOME team -- all GNOME 2.12.x ports use it. Preliminary documentation can be found at: http://people.FreeBSD.org/~ade/autotools.txt which is in the process of being SGMLized before introduction into the Porters Handbook. Light blue touch-paper. Run. Notes: svn path=/head/; revision=148323
* The RABL (pronounced "rabble") server is a statistical, machine-automated andMarcus Alves Grando2005-10-085-0/+92
up-to-the-second blackhole list server designed to monitor global network activity and make decisions based on network spread and infection rate - that is, abuse from an address which has been reported by a number of participating networks. This is in far contrast to how most other blacklists function, where fallable humans (many with political agendas) must process thousands of reports and make decisions - many times after the fact. The RABL is fully reactive to new threats and can block addresses within seconds of widespread infection - good to know in this world of drone PCs and stolen accounts. The RABL server blacklists addresses until they have cleared a minimum duration (an hour by default) without any additional reporting, making the appeals process as simple as "fix your junk". The RABL is designed to function via automated machine-learning spam filters, such as Bayesian filters. Each participating network is granted write authentication in the blackhole list, to prevent abuse. A client tool is also provided. The RABL client is the lookup and reporting component of the RABL. It is necessary for performing streaming connection lookups and writing to the RABL (assuming you have an account). PR: 87096 Submitted by: Ion-Mihai "IOnut" Tetcu <itetcu@people.tecnik93.com> Notes: svn path=/head/; revision=144552