vulnerability.
- Add a file, installed to $DOCSDIR, with more explicit post-installation
instructions.
- Update $PKGMESSAGE to point to this new file.
- Add more explicit warnings in various places that MAIL_GID *must* be set at
build time if Mailman is to be used with an alternate (non-Sendmail) MTA.
- Bring port in line with other similar ports by NOT explicitly depending on
Apache. This is both more maintainable and allows the user greater scope
in setting up a custom configuration, including the use of an alternative
web server. (Also, Mailman _can_ be used without a web server.)
- Clean up which documentation files get installed to $DOCSDIR.
- Update $PKGREQ to depend explicitly on Python >= 2.1.3, and not just >= 2.1
- Document required value of $MAIL_GID for Exim4.
- Substantial rewrite of $PKGINSTALL:
- Simplified layout.
- More extensive error checking.
- More expressive and user-friendly output.
- Substantial rewrite of $PKGDEINSTALL:
- Simplified layout.
- More expressive and user-friendly output.
- Delete %%MAILMANDIR%%/data/last_mailman_version in DEINSTALL, and restore
it in POST-DEINSTALL if the entire Mailman installation has not been
removed. This file is required by Mailman's update script (run as part
of the installation procedure) to update active mailing lists.
- Delete the errorlog if it is the only existing logfile. This will
finally allow the mailman port/package to be completely and cleanly
deinstalled when there are no active lists or updated configuration.
- Bump $PORTREVISION, with apologies to those tracking the port.
It should now finally be possible to update a Mailman installation with
active mailing lists simply by deinstalling the port/package, and
reinstalling a later version (or by using portupgrade(1)). There are still
no guarantees, though, and a backup is thorouhly recommended.
- Refrain from invoking ${PERL}
- Call Mailman's distributed check_perms script post-installation to fix file
permissions instead of doing so manually. This is more modular and will
greatly ease maintenance of the port. It implies a level of trust in
check_perms... but then, installing and running any 3rd party software
implies a level of trust.
- Actually install the images for Mailman's web front-end to
${PREFIX}/www/icons, instead of depending on the user to do this in a
post-installation step. Add a new build-time variable to control the
location where these images are intstalled.
- Gratuitous change: Change the GNU logo and link in the footer of most
pages in Mailman's web front-end to a "Powered by FreeBSD" logo, and a link
to the FreeBSD home page. This was accomplished by:
- Patching the source to allow for multiple footer bars based on a new
configuration variable LOGO_OS. If LOGO_OS is set to 'FreeBSD', the
FreeBSD footer will be displayed; otherwise, it reverts to the default
GNU footer.
- Set LOGO_OS to 'FreeBSD' in the installed Defaults.py (The user may
override this in mm_cfg.py)
- Bump $PORTREVISION again. (Sorry guys.)
with Sendmail, if on a recent $OSVERSION. (Whoops!)
- Submitted by: Richard Kiss <kiss@hhn.com>
- Clarify $PKGMESSAGE and output of $PKGDEINSTALL somewhat.
- Correctly handle Mailman config file (mm_cfg.py) in $PLIST when
deinstalling port/package.
- Bump PORTREVISION again.
- Add a $PKGDEINSTALL script to allow the port to clean up after itself
- Automatically create Mailman user's crontab(5) entry upon port/package
installation, and remove it upon deinstallation.
- Intended $PKGINSTALL according to personal taste. Converted tabs to
spaces.
- Remove some extraneous comments from the port's Makefile. (Oops)
- Further streamline @exec's in $PLIST.
- Bump PORTREVISION
- The reworking of this port is an ongoing process - Mailman users, please
bear with me!
maintaining most of the port's existing structure. A more comprehensive
restructuring of this port is in the works.
- Assume maintainership, pending any objections from -ports.