[aur-general] Packaging releases from git.kernel.org
I struggled a bit to package a tagged stable release from git.kernel.org to complement the -git package, finally figured out a method that's simple[1] but hidden from the cgit webUI; wanted to add to the wiki as a FAQ/tip for others. Would this be the right page?
https://wiki.archlinux.org/index.php/Arch_User_Repository
If not, better idea where to share the method? Not finding anything that looks right from the category page https://wiki.archlinux.org/index.php/Category:Package_development dedicated to git/svn build tips for AUR... ?
-te
[1] https://aur.archlinux.org/packages/tr/trace-cmd/PKGBUILD
On Fri, 30 Jan 2015 at 16:50:13, Troy Engel wrote:
I struggled a bit to package a tagged stable release from git.kernel.org to complement the -git package, finally figured out a method that's simple[1] but hidden from the cgit webUI; wanted to add to the wiki as a FAQ/tip for others. Would this be the right page?
https://wiki.archlinux.org/index.php/Arch_User_Repository
If not, better idea where to share the method? Not finding anything that looks right from the category page https://wiki.archlinux.org/index.php/Category:Package_development dedicated to git/svn build tips for AUR... ?
-te
[1] https://aur.archlinux.org/packages/tr/trace-cmd/PKGBUILD
On Fri, 30 Jan 2015 at 16:50:13, Troy Engel wrote:
I struggled a bit to package a tagged stable release from git.kernel.org to complement the -git package, finally figured out a method that's simple[1] but hidden from the cgit webUI; wanted to add to the wiki as a FAQ/tip for others. Would this be the right page?
I don't think so. A quick search didn't bring up a page that contains general packaging tips and I am not sure whether it is worthwhile to add such a page including tips similar to what you suggested. It might become cluttered with dozens of tips soon. Opinions?
By the way, is there any reason for not using Git tags to specify the snapshot tarball? Something along the lines of
source=("http://git.kernel.org/cgit/linux/kernel/git/rostedt/trace-cmd.git/snapshot/t...")
Otherwise, you need to look up the commit on every pkgver bump.
If not, better idea where to share the method? Not finding anything that looks right from the category page https://wiki.archlinux.org/index.php/Category:Package_development dedicated to git/svn build tips for AUR... ?
-te
[1] https://aur.archlinux.org/packages/tr/trace-cmd/PKGBUILD
On Fri, Jan 30, 2015 at 10:05 AM, Lukas Fleischer archlinux@cryptocrack.de wrote:
By the way, is there any reason for not using Git tags to specify the snapshot tarball? Something along the lines of
source=("http://git.kernel.org/cgit/linux/kernel/git/rostedt/trace-cmd.git/snapshot/trace-cmd-v${pkgver}.tar.gz")
hah! See, that's *exactly* what I was trying to figure out and it wasn't clear at all, the 'v' right before the version is the key thanks. I was digging around all the cgit and the git.kernel.org stuff and it's just not obvious like it is on github.com for releases. Thanks! :-) (hence, this would be a great tip on the wiki IMHO - some stuff is just not obvious, and my hack is "wrong" per se)
Off to update the package... -te
On 30/01, Troy Engel wrote:
On Fri, Jan 30, 2015 at 10:05 AM, Lukas Fleischer archlinux@cryptocrack.de wrote:
By the way, is there any reason for not using Git tags to specify the snapshot tarball? Something along the lines of
source=("http://git.kernel.org/cgit/linux/kernel/git/rostedt/trace-cmd.git/snapshot/trace-cmd-v${pkgver}.tar.gz")hah! See, that's *exactly* what I was trying to figure out and it wasn't clear at all, the 'v' right before the version is the key thanks. I was digging around all the cgit and the git.kernel.org stuff and it's just not obvious like it is on github.com for releases. Thanks! :-) (hence, this would be a great tip on the wiki IMHO - some stuff is just not obvious, and my hack is "wrong" per se)
Might want to find out who runs the kernel.org cgit instance and ask if they could add the snapshots option to their cgitrc, as that will add the links to snapshots of the given filetypes.
participants (3)
-
Johannes Löthberg
-
Lukas Fleischer
-
Troy Engel