[NEW PORT] mail/py-afew: Initial tagging script for notmuch mail

[dbaio]

Summary

[NEW PORT] mail/py-afew: Initial tagging script for notmuch mail

Its basic task is to provide automatic tagging each time new
mail is registered with notmuch.  In a classic setup, you might
call it after 'notmuch new' in an offlineimap post sync hook.

It can do basic thing such as adding tags based on email headers
or maildir folders, handling killed threads and spam.

In move mode, afew will move mails between maildir folders
according to configurable rules that can contain arbitrary
notmuch queries to match against any searchable attributes.

WWW: https://github.com/afewmail/afew

PR:	222629
Submitted by:	Sebastian Schwarz <[e-mail]>
Reviewed by:	mat, ???
Differential Revision:	DD12520

Test Plan

$ portlint -CA
looks fine.

poudriere testport:

poudriere OK with Python 2.7 and 3.6.

10.3-RELEASE-p21 amd64|i386
11.1-RELEASE-p1 amd64|i386
12.0-CURRENT 1200044 amd64|i386

[seschwar_gmail.com]

I see you added PKGNAMEPREFIX, @dbaio. I wasn't sure if this was required, since for example ansible and offlineimap don't use that and you can't install py27-afew and py36-afew at the same time.

[seschwar_gmail.com]

mail/py-afew/Makefile

23 ↗

(On Diff #33513)

As a Python port I'm thinking it should be architecture independent. However it includes *.pyc and *.pyo files. Are these architecture dependent?

[dbaio]

In D12520#260008, @seschwar_gmail.com wrote:

I see you added PKGNAMEPREFIX, @dbaio. I wasn't sure if this was required, since for example ansible and offlineimap don't use that and you can't install py27-afew and py36-afew at the same time.

It's better to follow the Python Ports Policy.

mail/py-afew/Makefile

23 ↗

(On Diff #33513)

Python bytecode is cross-platform.

[seschwar_gmail.com]

In D12520#260528, @dbaio wrote:

It's better to follow the Python Ports Policy.

I was actually looking for such a document. The Porter's Handbook seems to be mainly describing the mechanisms of how to get a port working. It is relatively light on the policies the created port should follow. Is there a reason this isn't part of the Porter's Handbook? Are there similar policy descriptions for ports in other programming languages?

[dbaio]

In D12520#260755, @seschwar_gmail.com wrote:

In D12520#260528, @dbaio wrote:

It's better to follow the Python Ports Policy.

I was actually looking for such a document. The Porter's Handbook seems to be mainly describing the mechanisms of how to get a port working. It is relatively light on the policies the created port should follow. Is there a reason this isn't part of the Porter's Handbook? Are there similar policy descriptions for ports in other programming languages?

There are some information in the Wiki kept by the teams, PortsTeams

[mat]

mail/py-afew/Makefile

26–27 ↗

(On Diff #33513)

If sphinx is only used for the docs, you might want to guard it by a DOCS option.

[dbaio]

Adding MANPAGES option

[dbaio]

sphinx is generating only a manpage, so I've added a MANPAGES option.

[seschwar_gmail.com]

mail/py-afew/Makefile

26–27 ↗

(On Diff #33513)

This command generates the manpages, not other additional documentation. Aren't manpages required to be included by default?

The FreeBSD Porter's Handbook notes:

The DOCS option only controls additional documentation installed in DOCSDIR. It does not apply to standard man pages and info pages.

So should a create a MANPAGES option just for the manual pages? Looking through the ports tree shows that only few ports bother doing so.

$ find /usr/ports -depth 3 -type f -name Makefile -print0 \
    | xargs -0 grep -F MAN \
    | grep -Fc OPTIONS_DEFINE
95

[seschwar_gmail.com]

Is there anything still blocking this from being committed to the ports tree?