Sure. I'll take ownership. Thanks for setting it up. The more visibility, the better. Let me know what I need to do.
I may have to rename my project. I'm finding "seer" is being used in so many projects already. I may call my project "seergdb", but still reference internally as "seer".
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi. You'll need to create an account on https://aur.archlinux.org/ if you don't have one already, and don't forget to link an SSH key in the account settings. After that, you can tell me your username and I'll add you to the maintainers of the package, then you should be able to clone the repo at ssh://aur@aur.archlinux.org/seer-gdb-git.git and push changes to it (using the mentioned SSH key). I can also stay a co-maintainer if you want.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi Ernie,
alright I added your username to the list of maintainers. You should now be able to clone the repo ssh://aur@aur.archlinux.org/seer-gdb-git.git and push changes to it.
You can find more information on how the AUR works here. But as this is a git package, it won't be needing much maintenance as it pulls the newest code automatically from the seer repository.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks. I think I understand. The git repo in ArchLinux references my repo in github. Anyone in the ArchLinux world can get my repo via the repo in AchLinix. And build it with ArchLinux makepck. Because it is a reference to my repo, ArchLinux will always be up to date.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi Ernie,
yes, pretty much. makepkg, upon invocation, pulls the source from the URL that the source variable inside the PKGBUILD file points to. The only part of that might break is the build function inside PKGBUILD, as the command cmake -S ${pkgname%-gdb-git}/src -B build -DCMAKE_BUILD_TYPE=Release relies on the fact that the root CMakeLists.txt file is located inside the seer src directory. Other than that package is bascially maintenance-free.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Originally posted by: epasveer
Hi Jorg,
Sure. I'll take ownership. Thanks for setting it up. The more visibility, the better. Let me know what I need to do.
I may have to rename my project. I'm finding "seer" is being used in so many projects already. I may call my project "seergdb", but still reference internally as "seer".
Originally posted by: jabra11
Hi. You'll need to create an account on https://aur.archlinux.org/ if you don't have one already, and don't forget to link an SSH key in the account settings. After that, you can tell me your username and I'll add you to the maintainers of the package, then you should be able to clone the repo at
ssh://aur@aur.archlinux.org/seer-gdb-git.gitand push changes to it (using the mentioned SSH key). I can also stay a co-maintainer if you want.Originally posted by: epasveer
Hi Jorg,
Done. My account name there is "epasveer".
Originally posted by: jabra11
Hi Ernie,
alright I added your username to the list of maintainers. You should now be able to clone the repo
ssh://aur@aur.archlinux.org/seer-gdb-git.gitand push changes to it.You can find more information on how the AUR works here. But as this is a git package, it won't be needing much maintenance as it pulls the newest code automatically from the seer repository.
Originally posted by: epasveer
Hi Jorg,
Thanks. I think I understand. The git repo in ArchLinux references my repo in github. Anyone in the ArchLinux world can get my repo via the repo in AchLinix. And build it with ArchLinux makepck. Because it is a reference to my repo, ArchLinux will always be up to date.
Originally posted by: jabra11
Hi Ernie,
yes, pretty much.
makepkg, upon invocation, pulls the source from the URL that thesourcevariable inside thePKGBUILDfile points to. The only part of that might break is thebuildfunction insidePKGBUILD, as the commandcmake -S ${pkgname%-gdb-git}/src -B build -DCMAKE_BUILD_TYPE=Releaserelies on the fact that the root CMakeLists.txt file is located inside the seersrcdirectory. Other than that package is bascially maintenance-free.Originally posted by: epasveer
Hi Jorg,
Thanks for your help. I'll have to try ArchLinux one of these day. Currently I'm on OpenSuse. (But I have lots of extra machines lying around :^)
I think I can close this task now...
Ticket changed by: jabra11
Originally posted by: epasveer
Closing task.