On 01/06/2012 10:57 PM, Magnus Therning wrote:
On Fri, Jan 06, 2012 at 07:41:32PM -0800, Don Juan wrote:
I am trying to update a AUR pkgbuild I found and the source file
when I download it has a - in the file name
name_2.0.1-beta1
I figure out using ${pkgver//_/-} converts it properly when listing
it as name_2.0.1_beta1.
The problem I have run into and can not seem to find info about or
something I have ever run into is that it seems bsdtar when
extracting is making the name as name_2.0.1-BETA1 and not making it
name_2.0.1-beta1 and makepkg fails saying it can not find the proper
file of name_2.0.1-beta1.
I have it as so in my PKGBUILD
package() {
cd ${srcdir}/${pkgname}_${pkgver//_/-}
also as
cd ${srcdir}/${pkgname}_${pkgver}
the tarball being downloaded converts properly and dl's fine, it
just seems to be in the next step for package, unless I just really
am not grasping this yet. If so feel free to say I need to read
more. But I think its something easy I am just looking over.
You do realise there is no *requirement* to use $pkgname and $pkgver,
right? You can just hard code the correct names into the PKGBUILD
and be done with it. The only drawback is that you need to modify a
few more places when updating the package in the future. That is a
*very* minor drawback in the vast majority of cases.
ahh, sorry I did not think of that, was trying hard to stick with what I
was reading that it slipped my mind. Working through updating the
patches on it now, just about finished building. I just picked a package
that was marked out of date to practice building with abs and using a
PKGBUILD. I will worry about the use of the variables in another package
I pick. I don't even need what I am trying to build :P Just wanted to
try and updated the build if I could.
Also, in the future consider uploading the PKGBUILD you are working on
to a pastebin. It will likely make it much easier to ask you
question. :-)
/M
@ Anthony & @Magnus
Noted about pasting to a board on-line will do next time.
Thanks for the help :)
