Bug 193721 - Proposed replacement for mail/filtermail
Summary: Proposed replacement for mail/filtermail
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Some People
Assignee: Kurt Jaeger
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-09-17 19:40 UTC by Mike Clarke
Modified: 2014-10-05 11:10 UTC (History)
1 user (show)

See Also:


Attachments
Proposed port for mail/filtermail (4.59 KB, text/plain)
2014-09-17 19:40 UTC, Mike Clarke
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Mike Clarke 2014-09-17 19:40:27 UTC
Created attachment 147412 [details]
Proposed port for mail/filtermail

mail/filtermail was recently deleted from the ports tree on account of not being staged. There had also been build errors with version 0.8.2.

I have created a port for filtermail-0.8.3 based on the old 0.8.2 port. This is staged and has been built and tested on 9.3-RELEASE and 10.0-RELEASE

Would it be possible to reinstate filtermail in the ports tree using the attached copy of the port?
Comment 1 Marcus von Appen freebsd_committer freebsd_triage 2014-10-03 07:05:52 UTC
Would you care to maintain it? We'd like to avoid (re)adding a port without a specific maintainer.
Comment 2 Mike Clarke 2014-10-04 15:15:14 UTC
(In reply to Marcus von Appen from comment #1)
> Would you care to maintain it? We'd like to avoid (re)adding a port without
> a specific maintainer.

Yes, I'm willing to maintain it, in which case the maintainer address should be  jmc-filtermail@milibyte.co.uk.

I should however point out that my programming skills are somewhat limited. I should cope OK with keeping it up to date but if any major problems arise I could be out of my depth and would need to rely on advice from the community. Version 0.8.2 was unchanged for 5 years until 0.8.3 came out in May this year so if the previous history is followed I don't expect there will be much attention needed.

A further point to consider is the use of the name filtermail. The original program is called mailfilter but the port and the program were renamed filtermail to avoid a conflict with an existing port. There is no longer a port called mailfilter so it is no longer essential to rename the port. Since filtermail 0.8.2 has already been deleted from ports then there might be something to be said in favour of re-introducing it as mailfilter.

Personally I'd be inclined to stick to filtermail as the name in order to maintain continuity but there doesn't seem to have been any complaints in the mailing lists about filtermail being deleted so perhaps continuity is no great issue.

Reverting the name to mailfilter would also avoid any implied association with the mail domain services provided by http://www.filtermail.com/

If it's felt that the port ought to be called mailfilter then perhaps now would be the most appropriate time to do so.
Comment 4 commit-hook freebsd_committer freebsd_triage 2014-10-05 11:09:37 UTC
A commit references this bug:

Author: pi
Date: Sun Oct  5 11:08:42 UTC 2014
New revision: 370055
URL: https://svnweb.freebsd.org/changeset/ports/370055

Log:
  mail/filtermail: resurrect, stage, 0.8.2 -> 0.8.3, new maintainer

  PR:		193721
  Submitted by:	Mike Clarke <jmc-freebsd2@milibyte.co.uk>

Changes:
  head/mail/Makefile
  head/mail/filtermail/
  head/mail/filtermail/Makefile
  head/mail/filtermail/distinfo
  head/mail/filtermail/files/patch-src__Makefile.in