Thanks. This: http://www.archlinux.org/pacman/PKGBUILD.5.html#_development_directives explains a bit more, but does not state whether, if I define _gitroot and _gitname, pkgver is optional. I tested it, and pkgver is neccessary. However, this is absurd and should be changed in a patch. I'll try to patch it tomorrow evening, along with PKGBUILD's manpage and the wiki page. Regards, M On Fri, Aug 3, 2012 at 6:37 PM, arielp <ariel@drakkn.net> wrote:

On 8/3/2012 6:56 AM, Menachem Moystoviz wrote:

...

I am a bit confused regarding makepkg's versioning of packages. From what Allan said on this mailing list a couple of days ago, custom support is being added to makepkg. In addition, from what I can see on the wiki and manpages, the only variable influencing the versioning is pkgver. However, from what I've heard, when running makepkg with _gitroot and _gitname set, makepkg will automatically set pkgver to the date of the last commit.

Could someone clarify this? Also, the wiki pages regarding makepkg should mention this. Thanks,

M

It uses the revision number from the repo. There is (used to be?) a wiki page that detailed how to use the VCS variables. This is the closest I could find: https://wiki.archlinux.org/index.php/Arch_CVS_%26_SVN_PKGBUILD_guidelines

-A

On Fri, Aug 3, 2012 at 6:58 PM, Florian Pritz <bluewind@xinu.at> wrote:

On 03.08.2012 17:55, Menachem Moystoviz wrote:

...

I'll try to patch it tomorrow evening, along with PKGBUILD's manpage and the wiki page.

Wait for the next pacman version because all this VCS code is being rewritten. Check the pacman-dev mailing list archives for more details.

PS: Also please stop top posting. Thank you.

-- Florian Pritz

Was I top-posting? Sorry. GMail's interface is notorious for automatically putting you in top-post mode. Thank you for the suggestion. M