Package Details: afew-git 1:2.0.0.r38.gf581330-1

Git Clone URL: (read-only, click to copy)
Package Base: afew-git
Description: Initial tagging script for notmuch mail
Upstream URL:
Licenses: custom:BSD
Conflicts: afew
Provides: afew
Submitter: kazuo
Maintainer: grazzolini (polyzen)
Last Packager: grazzolini
Votes: 12
Popularity: 0.000000
First Submitted: 2011-12-04 03:59 (UTC)
Last Updated: 2020-03-06 11:32 (UTC)

Latest Comments

grazzolini commented on 2020-03-06 11:33 (UTC)


I have added python-freezegun to makedepends, thanks for the info.

apetresc commented on 2020-03-05 20:37 (UTC)

There should be a make dependency on python-freezegun. It's needed for the tests that the PKGBUILD indirectly runs.

demize commented on 2018-08-01 00:10 (UTC)

dbacl has been unneeded since 1.1.0.

grazzolini commented on 2017-08-25 14:47 (UTC)

@timofonic This is something you might ask with upstream, I'm just the packager. Having said that, you can apply whatever arbitrary tags you want on emails and they get synced back to gmail, depending on what software you're using.

timofonic commented on 2017-08-25 14:23 (UTC)

Can this software have equivalent functionality to gmailieer? Can it have a workaround to get muted messages ( 2015 bug, they aren't going to fix it because this gives advantage to their webmail and native apps platforms).

lucc commented on 2017-08-07 16:21 (UTC)

Can you add "--tags" to the call to "git describe"? Upstream (sometimes?) uses unannotated tags for releases.

grazzolini commented on 2017-08-07 14:03 (UTC)

@mkaito I have been using afew with python 3 for years now. Were exactly is afew's official position on this?

mkaito commented on 2017-08-07 12:13 (UTC)

When you update, you might want to switch to python2. Afew's official position right now is that py3 doesn't work well enough to call it supported. We're working on it, but you should stick to py2 for now.

mkaito commented on 2017-03-22 10:43 (UTC)

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 (UTC)

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 (UTC)

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 (UTC)

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 (UTC)

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

cagprado commented on 2013-08-26 20:22 (UTC)

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 (UTC)

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

kazuo commented on 2013-06-11 12:17 (UTC)

@yardenac 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 (UTC)

@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. Thanks!

kazuo commented on 2013-05-28 15:19 (UTC)

@yardenac 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?

yar commented on 2013-05-24 19:20 (UTC)

afew supports both python2 and python3 - how would you feel about repackaging this for python3 as well? See how the notmuch does it here: