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.
writing of "Status:" and "X-UIDL:" headers. However, that only
happens with "Status:" header. Have qpopper honor it for "X-UIDL"
one as well.
o Bump PORTREVISION
PR: 73336
Submitted by: Helge Oldach <mail-qpopper-uidl@oldach.net>
Begin autotools sanitization sequence by requiring ports to explicitly
specify which version of {libtool,autoconf,automake} they need, erasing
the concept of a "system default".
For ports-in-waiting:
USE_LIBTOOL=YES -> USE_LIBTOOL_VER=13
USE_AUTOCONF=YES -> USE_AUTOCONF_VER=213
USE_AUTOMAKE=YES -> USE_AUTOMAKE_VER=14
Ports attempting to use the old style system after June 1st 2004 will be
sorely disappointed.
Update OpenSSL-support, include security/openssl/bsd.openssl.mk,
remove usage of deprecated librsaref/libRSAglue, add a knob WITHOUT_SSL.
Pacify portlint.
Terminate all sentences in comments with a period.
Replace spaces with tabs in pre-everything:: messages to print out
an aligned table.
PR: ports/53401
Submitted by: Marius Strobl <marius@alchemy.franken.de>
(Committed on behalf of lioux@, who is having machine problems)
the user to specify a different logging facility
Submitted by: Christophe Labouisse <christophe@labouisse.org>
Reviewed by: knu
Approved by: portmgr (knu)
o Add options:
- WITH_PAM and WITH_STANDALONE_MODE [1]
- WITHOUT_IPV6 [2]
- WITHOUT_U_OPTION [3]
o Remove patch merged into distribution
Submitted by: Sean Wal <sean0x77@yahoo.com> [1]
Prompted by: too many [2],
"Karsten W. Rohrbach" <karsten@rohrbach.de> [3]
2048 characters is sent to the qpopper process, a denial of service
condition will occur"
Actually, this is caused by an incorrect assumption. qpopper uses
the same buffer over and over when communicating. However, it never
makes sure that the buffer has been updated if something goes wrong.
Therefore, one can try to add to this buffer over and over; thus,
consuming available resources.
Solution, do not follow unofficial patch available in bugtraq mailing
list since losing pointer references is not an option. Otherwise,
change the way both getline and tgetline functions work. Just so
that they resemble read(2) return codes as follows:
1) if < 0 problem
2) if >= 0 user typed something (enter without anything else is
something)
First patch sent by Isao SEKI <iseki@gongon.com>
PR: 36326
Prompted by: Alessandro de Manzano <ale@unixmania.net>,
Isao SEKI <iseki@gongon.com>
Reviewed by: eivind,
Alessandro de Manzano <ale@unixmania.net>,
David Rufino <dr@soniq.net>,
Isao SEKI <iseki@gongon.com>
cannot log in the popper daemon, let the users decide for either
a default file (use a copy of the system's /etc/ftpusers file)
or an empty file
2) also, make the installation of this file prefix safe and name
it popusers (PREFIX/etc/qpopper/popusers). This changes expected
behavior of the port
3) add a PKGINSTALL script to handle this file install/deinstall
4) style changes: use variables to make the port easier to maintain
Prompted by: Dan Langille <dan@langille.org>
Reviewed by: freebsd-ports (silence), kris, sobomax
o Several fixes
o Improvements to poppassd
o Remove extra-patch since it has been merged into the distribution
Prompted by: Brett Jackson <brett@modlogic.com>, sudz@ns3g.com,
Mars G Miro <mars@cannoncreek.com>
gdbm port (--without-gdbm)
o USE_AUTOCONF due to files/patch-configure.in rev 1.1
o update ipv6 patch to version 20010504
o move all options to WITH_* options, let the older
options work for a while
o advertise all WITH_* options
o add WITH_POPPASSD support (Hajimu Umemoto contribution)
PR: 27093
Submitted by: Hajimu Umemoto <ume@mahoroba.org>,
K Karthik <kar_alerts@mglorysb.com>
freeze is coming today, so I decided to force things a little. Among other
things this release supports TLS/SSL, previously available in the Qualcomms's
commercial package "Qpopper LX".