Bug 87212
| Summary: | [update] mail/qmrtg update to version 2.1 | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Ports & Packages | Reporter: | mij <mij> | ||||
| Component: | Individual Port(s) | Assignee: | Renato Botelho <garga> | ||||
| Status: | Closed FIXED | ||||||
| Severity: | Affects Only Me | ||||||
| Priority: | Normal | ||||||
| Version: | Latest | ||||||
| Hardware: | Any | ||||||
| OS: | Any | ||||||
| Attachments: |
|
||||||
Responsible Changed From-To: freebsd-ports-bugs->garga I can take it. State Changed From-To: open->feedback What do you think about add this new port as qmrtg2? State Changed From-To: feedback->closed Committed. Thanks! |
This patch upgrades mail/qmrtg/ to version 2.1. Changelog includes: - completely new analyzers, more fast, powerful and reusable - capability to monitor DNSBL (rbl) - way easier extensibility - vastly improved documentation No files have been added to the port; the following disappeared: files/patch-qmrtg.sh files/patch-qmrtgsync.sh files/ `portlint -A` reports 3 fatals on this port, about the usage of WITHs before the inclusion of pre.mk. This is known, as the usage is just setting defaults in case of non-interactive run. Also, the port creates a directory with absolute path, /var/db/${PORTNAME}, removed in deinstall. This is also known and under control. This version of the software itself is no longer compatible with config files from older versions, so upgrading will break a working scenario. I don't know if there's any best-practice for notifying the user about this; it's just told in pkg-message as of now.