Package Details: afew-git 1:0.237.162d9fa-1

Git Clone URL: (read-only)
Package Base: afew-git
Description: afew is an initial tagging script for notmuch mail
Upstream URL:
Licenses: custom:BSD
Submitter: kazuo
Maintainer: mlq
Last Packager: mlq
Votes: 9
Popularity: 0.253159
First Submitted: 2011-12-04 03:59
Last Updated: 2015-11-23 08:17

Latest Comments

mkaito commented on 2017-03-22 10:43

Just a reminder: `pkgver` still doesn't work. Refer to @cagprado's comment. I'm going to flag this out of date, just to poke @mlq.

cagprado commented on 2017-02-17 08:27

makepkg refuses to build due to most recent tags in git rep containing forbidden characters for pkgver. Using the first suggested approach at seems to work.

lucc commented on 2015-11-24 08:11

Thanks but can you also bump the $pkgrel, please. Otherwise users (or aur helpers like yaourt) might not notice the change.

lucc commented on 2015-11-23 08:09

Please add the man page to the package. It can be build with

make -C docs man

and installed with

install -D -m 644 docs/build/man/afew.1 "$pkgdir/usr/share/man/man1"

or with

mkdir -p "$pkgdir/usr/share/man/man1"
gzip < docs/build/man/afew.1 > "$pkgdir/usr/share/man/man1/afew.1.gz"

The package needs to makedepend on python-shpinx in order to build the man page.

kazuo commented on 2013-08-26 21:36

Thanks for it, you are right. Sorry for not testing it thorough, this is my mistake.

cagprado commented on 2013-08-26 20:22

Oh sorry… my mistake, python-setuptools is required for running the program, not just building it.

Cheers, ;)

cagprado commented on 2013-08-22 15:38

Should’t the package also makedepend on python(2)-setuptools?


kazuo commented on 2013-06-11 12:17


Thanks for the information and I'm very sorry for the late reply.

I fail to see why you need the bindings but not the bin/afew, but if this is your user case I will package both bindings and make bin/afew to use the python3 bindings and optdep to python2.

Please take a look at the new PKGBUID and see if this is fitting.

Thanks again!

yar commented on 2013-06-03 17:33

@kazuo: Personally, I'm interested in the bindings for python3.

More generally, best practice is to default to (depend on) python3 whenever possible while providing python2 as an option (optdepends) for now. Eventually python2 will go away.


kazuo commented on 2013-05-28 15:19


What notmuch do is package both python2 and python3 bindings.

What are you proposing for afew package to do? As a program, not only bindings, I need to make it depends (not only optdepends) on python2 or python3 and we don't have a generic provider for python.

I can ship both libraries but the /usr/bin/afew will point to only one of then.

I can change it for python3 only, what you think?

All comments