XFree86 (3 or 4) to depend to when USE_XLIB is set.
XFREE86_VERSION defaults to 3 for now, but adventurous users can
override it in /etc/make.conf. When XFREE86_VERSION=3, USE_XLIB
will add a dependency to x11/XFree86; when it is set to 4, the
dependency will be to x11/XFree86-4-libraries. When
XFREE86_VERSION=4, the PKG_IGNORE_DEPENDS and ALWAYS_BUILD_DEPENDS
hacks to avoid messing with XFree86 are turned off.
Since XFree86 version 4 includes some software that used to be
separate ports, when XFREE86_VERSION=3 the following variables are
provided:
USE_DGS LIB_DEPENDS on x11/dgs
USE_FREETYPE LIB_DEPENDS on print/freetype
USE_MESA LIB_DEPENDS on graphics/Mesa3
USE_XPM LIB_DEPENDS on graphics/xpm
When XFREE86_VERSION=4, these variables have no effect. The
LIB_DEPENDS in the tree for the above four ports have all been
converted to the USE_* counterparts. For your information, this
is the count of the number of ports:
USE_DGS 0
USE_FREETYPE 16
USE_MESA 36
USE_XPM 236
There is a new variable, XAWVER, which is set to 6 when
XFREE86_VERSION=3 and 7 when XFREE86_VERSION=4. This is also
passed to PLIST_SUB so ports that build Xaw based shared libraries
can use this variable to substitute the shlib version number.
There is also a provision of using a separate mtree file for
XFREE86_VERSION=4, but that part is not enabled yet.
Reviewed by: the ports list
Tested by: make index (XFREE86_VERSION=3 only)
(2) Add hebrew to list of valid categories.
Submitted by: nbm
Mail::Sender provides an object oriented interface to sending mails.
It doesn't need any outer program. It connects to a mail server
directly from Perl, using Socket.
PR: 20208
Submitted by: ben
manpage-patch-files.
However, due to an odd bug in patch(1), 2 of the 3 hunks for
popper.8 fails (somehow, diff(1) thinks it is a binary file and
patch cannot patch it correctly if diff is used with the -a option).
So patch-ac only changes /usr/local/lib/popper to .../libexec/qpopper
and doesn't neither corrects the location of sendmail nor adds the
/etc/ftpusers file to the SEE ALSO section.
In the Makefile, /usr/local is now replaced with PREFIX for both manpages.
As Vladimir Ivanov explains:
unix-mx driver doesn't set file permissions properly for non-private
messages (e.g. public#). The problem caused by mx_append procedure,
where the driver doesn't call set_mbx_permissions for just created
message file.
Submitted by: Vladimir Ivanov <wawa@comptek.ru>
Renames port to qpopper, since this is the official name Qualcomm gives it.
Add pkg/MESSAGE for the inetd.conf line.
Create ${PREFIX}/etc/popper directory also for pkg's.
PR 18568 (Sent in by Jeff Palmer <jeff@isni.net>) gave me the idea for
this update.
The mail/imap-uw port used to build a shared library version of cclient
of it's own (in fact, this is where much of the infrastructure for the
cclient port came from). However, since more things depend on cclient
then just UW's imap server, I broke them into separate ports.
From now on, nothing should have to depend on imap-uw just to get
c-client.
PR: 19749
Submitted by: kbyanc@posi.net
Pine has historically built against an internal copy of the c-client library,
however c-client development has progressed beyond what is shipped with pine.
(It would appear that all new development work is being done via UW's imap
server codebase.) This change allows pine to utilize improvements/bugfixes in
the c-client library. In addition, the cclient port builds c-client as a
a shared library. Now, pine links against this shared library. As a result,
pine binaries are approximately 550k smaller. On the other hand, the c-client
library itself is a good 650k. The real benefit here is that c-client may be
shared amongst multiple binaries (i.e. imap-uw, php, and perl scripts using the
p5-Mail-CClient module), thereby potentially reducing the overall disk and
memory usage.
PR: 19731
Submitted by: kbyanc@posi.net
Reviewed by: will
Mailman is software to help manage email discussion lists, much like Majordomo
and Smartmail. Unlike most similar products, Mailman gives each mailing list a
web page, and allows users to subscribe, unsubscribe, etc. over the web. Even
the list manager can administer his or her list entirely from the web. Mailman
also integrates most things people want to do with mailing lists, including
archiving, mail-to-news gateways, integrated bounce handling, spam prevention,
email-based admin commands, direct SMTP delivery (with fast bulk mailing),
support for virtual domains, and more.
PR: 19400
Submitted by: Nick Hibma <n_hibma@calcaphon.com>
