[aur-general] Package ownership change request for yaourt-git

Daniel Wallace danielwallace at gtmanfred.com
Sun Aug 3 23:12:55 EDT 2014

Anyone using VCS packages from the AUR, should be following the package
upstream and rebuilding it as they go.  It is not meant for someone that is
just casually using the package.

The package version should be updated each time you build the package,
specified in the pkgver() function.


Because the version is changed whenever you rebuild it, it can't really be
marked out of date, you should be tracking your packages and rebuilding
them when new features are added or things are changed in order to test
direct upstream packages.


> Date: Sun, 3 Aug 2014 23:06:46 -0400
> From: ichimonji10 at gmail.com
> To: aur-general at archlinux.org
> Subject: Re: [aur-general] Package ownership change request for yaourt-git
> > Really, most ofthis is mostly irrelevant TBH.
> This is a common point of confusion. Because of this, I think it is worth
> addressing and therefore relevant.
> > The official way of using the PKGBUILDs is manually with makepkg.
> I suspect that the usual use case for interacting with the AUR is with an
> AUR helper. I think this qualifies it as subject matter that a capable
> package maintainer should have some familiarity with, even though this use
> case may be disagreeable to you personally.
> > the only times an AUR VCS package is out-of-date is when it's broken in
> some way
> Assuming that AUR helpers are a common tool for interacting with the AUR,
> VCS packages in the AUR are out-of-date when their version number is...
> out-of-date.
> Finally, the situations that trigger a VCS package update should be
> identical whether a package is in the AUR or one of the more official repos.
> — Jeremy "Ichimonji10" Audet

More information about the aur-general mailing list