On Wed, Apr 03, 2013 at 02:29:45PM -0500, Doug Newgard wrote: > ---------------------------------------- > > Date: Wed, 3 Apr 2013 15:24:06 -0400 > > From: [email protected] > > To: [email protected] > > Subject: Re: [aur-general] pacman 4.1 (makepkg 4.1) git pkgver autobump > > problem > > > Under Guidelines: > > > "As of pacman 4.1, pkgver gets some special treatment. If pkgver is > > > empty, makepkg looks for a pkgver() function. This can be one of many > > > things, outlined below:" > > That's definitely not the case; pacman-git [1], for example, has a > > non--empty pkgver, has a pkgver() provided, and the pkgver variable > > updates just fine when I build it. It doesn't have to be empty (at least > > atm).
Yeah. I just wanted to know what to fix. > > > > > > [1] https://aur.archlinux.org/packages/pa/pacman-git/PKGBUILD > > Yes, I'm aware of that. If you read the quote of the previous email, > KaiSforza was asking where the incorrect info is and I was pointing him to > it. Thanks, fixed it. -- William Giokas | KaiSforza GnuPG Key: 0x73CD09CF Fingerprint: F73F 50EF BBE2 9846 8306 E6B8 6902 06D8 73CD 09CF
pgpLFoBsIz7im.pgp
Description: PGP signature
