Add a Archlinux PKGBUILD #2
Conversation
|
Hey @chabad360 , Thanks for taking the time to make this. This looks like a reasonable start for a PKGBUILD file. I found this as a source of info[1] What I could not find is any example a go project (or any project) that keeps a PKGBUILD file in the source tree. I checked the github pages of the example packages mentioned in [1]. So I'm just not sure where the PKGBUILD is supposed to live for a project Can you shed any extra light on this? Thanks in advance ! -TW [1]https://wiki.archlinux.org/index.php/Go_package_guidelines |
|
Generally speaking, a package for a distro is maintained by the distro
itself, therefore the config for building that package wouldn't be in
upstream.
In our case (Archlinux), the PKGBUILD is pushed to the Arch User
Repository (AUR)[0] where it's downloaded by the user and built
locally, or it's an official package and is downloaded through the
package manager.
The pkgbuild usually won't live with the project, but I don't see an
actual reason why that's an issue.
…On 12/18/19, TekWize.ly ***@***.***> wrote:
Hey @chabad360 ,
Thanks for taking the time to make this.
This looks like a reasonable start for a PKGBUILD file.
I found this as a source of info[1]
What I could not find is any example a go project (or any project) that
keeps a PKGBUILD file in the source tree.
I checked the github pages of the example packages mentioned in [1].
I even searched github looking for projects with a PKGBUILD file[2] and
couldn't find any clear examples of projects keeping their PKGBUILD file in
the source tree.
So I'm just not sure where the PKGBUILD is supposed to live for a project
Can you shed any extra light on this?
Thanks in advance !
-TW
[1]https://wiki.archlinux.org/index.php/Go_package_guidelines
[2]https://github.com/search?q=filename%3APKGBUILD
--
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
#2 (comment)
--
Mendel G
chabad360@gmail.com
|
|
Hey @chabad360 ! Q: What are the steps to getting this into AUR ? Do I need to create an account / submit a request / etc ? Q: Whats the best / easiest way to test this PKGBUILD file locally? I tried starting an archlinux docker image and running makepkg but I think I'm still missing a few key points. Thanks again for the assist - Now that the project is in homebrew, I'm excited to try to get into other package managers. |
Well, I've done you one more, and already uploaded it to the AUR, if you want I'll hand over the package maintenance to you.
You'll need to install the |
|
OK I was able to test the file from this pr and build a tgz with /usr/bin/run and the LICENSE file, so thats cool! Also cool that you already submitted a build to AUR !! Some Q's regarding differences between that build file and this one: Is that version number normal? ie Was there a reason it needed to be named I don' t enough about either, just wondering why the change? Lastly, Q: Has that build file been deployed or is it still pending some kind of approval? Thanks again! PS: Lastly lastly Q: Are you using run much at all, I'd love to hear how its working for you |
The
This is the naming convention for packages that are built from the git upstream.
It's been deployed.
I haven't gotten much of a chance yet, as I'm busy with some other things, but once I get the chance, I'll be glad to my two cents. |
|
@chabad360 Thanks for the detailed response !
Indeed I have several releases - Just tagged
SWEET - Ok so how would I use the deployed version to install run? i.e say I started from a fresh arch docker image, what would I type to install run within that image using the deployed pkg file? Depending on how easy it is, it might be time for me to add a section in the README for it. As always, thank you ! -TW |
|
There's no need for adding instructions to the README, just put a link to it, and Arch users will know what to do.
It doesn't get picked up by the AUR, it's only checked locally on build. P.s. if you give me some time, I'll put up a PKGBUILD for the pre-built binaries. |
|
Hey @chabad360,
That sounds great ! Q: Would you be able to submit an PR to update the Install section of the README with information that Archlinux users would find useful? Lemme know, and have a great weekend! -TW |
|
Done #24 |
|
Hey @chabad360 , In adding NPM support, I decided to use the With that pattern established, I'm okay storing this file within that folder structure as well. Could you please:
Thank you and please let me know if you have any questions. -TW |
|
Done! |
|
Thanks ! @all-contributors please add @chabad360 for infra |
|
I've put up a pull request to add @chabad360! 🎉 |
This would be a first step for making binary packages generally available (although in this current state you'd push just the
PKGBUILDand its corresponding.SRCINFOto the Archlinux aur and people would download thePKGBUILDand build it), you can usemakepkg(on arch) to build a.pkg.tar.xzthat would go with a release.