You are not logged in.
Pages: 1
How would I get around pkgver not being able to use dashes on a version number like 1.3.0-alpha4. I am looking for a method that lets me use variables to download source and make the package with dashes.
pkgver=1.3.0
?=-alpha4
I was thinking something like above would work but it's just a guess (of course the ? would be replaced with a real variable name I just don't know one atm)
Offline
How about a version number like 1.3.0alpha4? Dashes are not supported in the pkgver.
Offline
The above example is from audacious which I have no control over the package naming. I would need to download the source and manually rename it to make is compatible and that's why I was looking for a second variable that could handle the -alpha4. This of course would be fine for private packages but not for ones that I would like to upload to aur.
Offline
from memory a forward slash should precede a dash and an underscrore for example
$pkgname-$pkgver\-alpha4
The -alpha4 part has to be left out of the $pkgver variable. Then again there is probably a very simple way to create your own variables in PKGBUILDS that someone smarter than me will know.
Last edited by clarence (2007-02-09 04:56:45)
fck art, lets dance.
Offline
Isn't there an audacious package already in AUR?
Edit: just checked and the package audacious-player-svn is already in AUR.
Offline
The above example is from audacious which I have no control over the package naming. I would need to download the source and manually rename it to make is compatible and that's why I was looking for a second variable that could handle the -alpha4. This of course would be fine for private packages but not for ones that I would like to upload to aur.
You don't have to use the $pkgver and $pkgname variables to download the source.
How about:
pkgver=1.3.0alpha4
_realver=1.3.0-alpha4
source=(some://url.to/$pkgname-$_realver)
Offline
Then again there is probably a very simple way to create your own variables in PKGBUILDS that someone smarter than me will know.
Yeah, that'll be phrakture.....
fck art, lets dance.
Offline
iBertus:
I am aware of the svn package in aur I was just using audacious as a example.
phrakture:
That was the answer I was looking for thank you.
Offline
How about linuxwacom package?
Previous version was 0.8.0 => AUR "version-release" 0.8.0-1
New version is 0.8.0-1 and i don't know what to do :-\
Version tags may not include hyphens!
UPD!
Also it conflicts with The Arch package making HOW-TO - with guidelines:
...if the package writer uses a dash in their version numbering scheme, replace it with an underscore. ('0.99-10' => '0.99_10')
Just need developers blessing for this
pkgver=0.8.0_1
pkgrel=1
Last edited by Ilya (2008-05-11 00:17:15)
Offline
Just need developers blessing for this
pkgver=0.8.0_1 pkgrel=1
How about a TUs blessing. Sometimes, I would just use 0.8.0.1 in that situation. But be careful, because if they actually release a version numbered that you will run into trouble... So the above way is safer.
Offline
How about a TUs blessing.
oh, yes, sorry, thanks
Offline
The benefit of using a dash is that you can use bash substitution to easily turn it into a dash:
source=(http://www.blah.com/sources/$pkgname-${pkgver/_/-}.tar.gz)
Offline
Pages: 1