[aur-general] PKGBUILD/AUR help
I'm trying to enhance the PKGBUILD of kernel26-pf to detect the cpu-specific .config option and automatically add it to the generated package and its description, by tweaking the $PKGEXT and $pkgdesc variables. Example: an amd64-k8 optimized kernel would be packaged as kernel26-pf-2.6.35-pf7-k8.pkg.tar.xz. The PKGBUILD I've created (see http://pastebin.ca/1931033 - relevant lines 96-138) builds and creates the package just fine using makepkg, but submission of the source package to AUR fails. I know that $PKGEXT perhaps shouldn't be tampered with, but I'm open to suggestions.
I'm trying to enhance the PKGBUILD of kernel26-pf to detect the cpu-specific .config option and automatically add it to the generated package and its description, by tweaking the $PKGEXT and $pkgdesc variables. Example: an amd64-k8 optimized kernel would be packaged as kernel26-pf-2.6.35-pf7-k8.pkg.tar.xz. The PKGBUILD I've created (see http://pastebin.ca/1931033 - relevant lines 96-138) builds and creates the package just fine using makepkg, but submission of the source package to AUR fails. I know that $PKGEXT perhaps shouldn't be tampered with, but I'm open to suggestions.
The stubborn source package can be found at http://omploader.org/iNWYyMA, if any TU wants to test.
On Thu 02 Sep 2010 12:02 +0300, Christos Nouskas wrote:
I'm trying to enhance the PKGBUILD of kernel26-pf to detect the cpu-specific .config option and automatically add it to the generated package and its description, by tweaking the $PKGEXT and $pkgdesc variables. Example: an amd64-k8 optimized kernel would be packaged as kernel26-pf-2.6.35-pf7-k8.pkg.tar.xz. The PKGBUILD I've created (see http://pastebin.ca/1931033 - relevant lines 96-138) builds and creates the package just fine using makepkg, but submission of the source package to AUR fails. I know that $PKGEXT perhaps shouldn't be tampered with, but I'm open to suggestions.
I think you should probably put that info in the $pkgname rather than $PKGEXT. I don't think that should have any effect on the AUR however. Last I checked it will try to deal with any .tar.gz.
Loui Chang wrote:
On Thu 02 Sep 2010 12:02 +0300, Christos Nouskas wrote:
I'm trying to enhance the PKGBUILD of kernel26-pf to detect the cpu-specific .config option and automatically add it to the generated package and its description, by tweaking the $PKGEXT and $pkgdesc variables. Example: an amd64-k8 optimized kernel would be packaged as
I think you should probably put that info in the $pkgname rather than $PKGEXT. I don't think that should have any effect on the AUR however. Last I checked it will try to deal with any .tar.gz.
That's what I ended up with. It took me a while to realize that the AUR parser doesn't always like variable changes midway through the PKGBUILD, so I additionally request some TU to delete my failed http://aur.archlinux.org/packages.php?ID=40533 -- X.
On Sep 4, 2010, at 5:47 PM, Christos Nouskas
Loui Chang wrote:
On Thu 02 Sep 2010 12:02 +0300, Christos Nouskas wrote:
I'm trying to enhance the PKGBUILD of kernel26-pf to detect the cpu-specific .config option and automatically add it to the generated package and its description, by tweaking the $PKGEXT and $pkgdesc variables. Example: an amd64-k8 optimized kernel would be packaged as
I think you should probably put that info in the $pkgname rather than $PKGEXT. I don't think that should have any effect on the AUR however. Last I checked it will try to deal with any .tar.gz.
That's what I ended up with. It took me a while to realize that the AUR parser doesn't always like variable changes midway through the PKGBUILD, so I additionally request some TU to delete my failed http://aur.archlinux.org/packages.php?ID=40533
-- X.
Done.
participants (3)
-
Brad Fanella
-
Christos Nouskas
-
Loui Chang