Warning: file_exists(): open_basedir restriction in effect. File(/srv/http/vhosts/aur.archlinux.org/public/web/locale//en/LC_MESSAGES/aurweb.mo) is not within the allowed path(s): (/srv/http/vhosts/aur-dev.archlinux.org/:/etc/aurweb/) in /srv/http/vhosts/aur-dev.archlinux.org/public/web/lib/streams.php on line 90
AUR (en) - astroid

Notice: Undefined variable: name in /srv/http/vhosts/aur-dev.archlinux.org/public/web/lib/pkgfuncs.inc.php on line 248

Package Details: astroid 0.7-1

Git Clone URL: https://aur-dev.archlinux.org/astroid.git (read-only)
Package Base: astroid
Description: a graphical threads-with-tags style, lightweight and fast, email client for notmuch, inspired by sup and others
Upstream URL: https://github.com/astroidmail/astroid
Keywords: mail
Licenses: GPL
Submitter: gauteh
Maintainer: gauteh
Last Packager: gauteh
Votes: 8
Popularity: 1.075088
First Submitted: 2015-09-20 10:24
Last Updated: 2017-01-02 22:16

Latest Comments

1 2 3 4 Next › Last »

gauteh commented on 2017-01-02 22:28

This is now the release package, a new -git package tracking master is available in astroid-git.

gauteh commented on 2016-12-16 13:51

@grazzolini:

Yeah :) In this case, we will have the astroid-git package that people can use - but they should generally be able to just get the release version if something breakes. Normally the -git package should remain stable. I will scale the development to have more stable master branch if/when contributions increase.

There are few things that are as disruptive as when the e-mail system suddenly breaks down, we are pretty sure to loose users quickly that way.

grazzolini commented on 2016-12-16 13:15

@gauteh

You'd be surprised at how few people stand by that definition. I agree with you, but I've seen enough of the contrary.

gauteh commented on 2016-12-16 09:02

No. A release should be a stable and tested point, so that people can always revert to the latest release with some confidence that it will work.

grazzolini commented on 2016-12-15 23:20

@gauteh
Yeah, that would require more releases. But you can always tag some point to be a release and move on.

gauteh commented on 2016-12-15 21:19

Yeah - I was thinking about maybe making two. This will be the release version then. I will fix after the next release, hope to have it out before christmas. Then I'll create a new -git package. I will have to make more frequent releases then.

grazzolini commented on 2016-12-15 11:59

@gauteh

You can upload a new PKGBUILD with -git and file a merge request with the new one. In the end there might be some breakage, but if you up the pkgrel afterwards, users of decent helpers, might not even notice the package rename.

Or, if you want, you could make this one a release version and build from a tagged release on github. And keep the -git one for people that want to build from git. If this package had more votes, I would consider it for inclusion in community. But it can't be a -git package in that case.

Cheers,
Giancarlo Razzolini

gauteh commented on 2016-12-15 09:16

@grazzolini: Thanks, nice to hear. Do I have to delete and re-upload the package to rename it?

grazzolini commented on 2016-12-15 03:12

@gauteh
Hi there,

I've been a (now) long time user of astroid and I must say that it is my daily driver for interacting with notmuch.

I recently become an Arch linux trusted user and I would like to ask you to rename this package to astroid-git. It is built from git, and this non VCS naming doesn't help to distinguish it from a release built package.

Also, I can't seem to build a package with the current .SRCINFO. I always need to manually run makepkg forcing a clean build dir.

Cheers,
Giancarlo Razzolini

gauteh commented on 2016-11-01 12:20

@grazzolini: should be fixed now, please try again.