[aur-general] pacman 4.1 (makepkg 4.1) git pkgver autobump problem
The problem: according to archwiki, to autobump pkgver, pkgver should be empty and pkgver() is provided. However, if we package it, the version number is empty, so AUR wont accept it. The Question: 1. is it a bug? 2. should aur be updated to allow empty pkgver? My idea: if pkgver=AUTO, then pkgver() must be provided and it will be called. otherwise, pkgver must be valid version number.
Just wrong (incomplete? unclear?) info. pkgver() will be run even if pkgver= isn't empty. Just upload it to the AUR with whatever pkgver= it has. ----------------------------------------
Date: Wed, 3 Apr 2013 10:21:12 -0700 From: tailinchu@gmail.com To: aur-general@archlinux.org Subject: [aur-general] pacman 4.1 (makepkg 4.1) git pkgver autobump problem
The problem: according to archwiki, to autobump pkgver, pkgver should be empty and pkgver() is provided. However, if we package it, the version number is empty, so AUR wont accept it.
The Question: 1. is it a bug? 2. should aur be updated to allow empty pkgver?
My idea: if pkgver=AUTO, then pkgver() must be provided and it will be called. otherwise, pkgver must be valid version number.
On Wed, Apr 03, 2013 at 10:21:12AM -0700, Tai-Lin Chu wrote:
The problem: according to archwiki, to autobump pkgver, pkgver should be empty and pkgver() is provided. However, if we package it, the version number is empty, so AUR wont accept it.
The Question: 1. is it a bug? 2. should aur be updated to allow empty pkgver?
My idea: if pkgver=AUTO, then pkgver() must be provided and it will be called. otherwise, pkgver must be valid version number.
This would fail miserably though as soon as someone updates their package without getting a new one from the AUR (which is kind of the point of a -git package), and no matter what is in the pkgver field, it will be updated. Also, what wiki page (and revision) did you see this about pkgver needing to be empty? (I just want to correct whatever it is I put in there that is wrong) Thanks, -- William Giokas | KaiSforza GnuPG Key: 0x73CD09CF Fingerprint: F73F 50EF BBE2 9846 8306 E6B8 6902 06D8 73CD 09CF
Also, what wiki page (and revision) did you see this about pkgver needing to be empty? (I just want to correct whatever it is I put in there that is wrong)
Thanks, -- William Giokas | KaiSforza GnuPG Key: 0x73CD09CF Fingerprint: F73F 50EF BBE2 9846 8306 E6B8 6902 06D8 73CD 09CF
https://wiki.archlinux.org/index.php/VCS_PKGBUILD_Guidelines 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:"
On 04/03/2013 02:51 PM, Doug Newgard wrote:
Also, what wiki page (and revision) did you see this about pkgver needing to be empty? (I just want to correct whatever it is I put in there that is wrong)
Thanks, -- William Giokas | KaiSforza GnuPG Key: 0x73CD09CF Fingerprint: F73F 50EF BBE2 9846 8306 E6B8 6902 06D8 73CD 09CF https://wiki.archlinux.org/index.php/VCS_PKGBUILD_Guidelines 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).
[1] https://aur.archlinux.org/packages/pa/pacman-git/PKGBUILD
----------------------------------------
Date: Wed, 3 Apr 2013 15:24:06 -0400 From: luolimao@gmail.com To: aur-general@archlinux.org Subject: Re: [aur-general] pacman 4.1 (makepkg 4.1) git pkgver autobump problem
On 04/03/2013 02:51 PM, Doug Newgard wrote:
Also, what wiki page (and revision) did you see this about pkgver needing to be empty? (I just want to correct whatever it is I put in there that is wrong)
Thanks, -- William Giokas | KaiSforza GnuPG Key: 0x73CD09CF Fingerprint: F73F 50EF BBE2 9846 8306 E6B8 6902 06D8 73CD 09CF https://wiki.archlinux.org/index.php/VCS_PKGBUILD_Guidelines 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).
[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.
On Wed, Apr 03, 2013 at 02:29:45PM -0500, Doug Newgard wrote:
----------------------------------------
Date: Wed, 3 Apr 2013 15:24:06 -0400 From: luolimao@gmail.com To: aur-general@archlinux.org 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
participants (4)
-
Doug Newgard
-
Limao Luo
-
Tai-Lin Chu
-
William Giokas