-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Publish package on AUR (arch linux user repo) #81
Comments
@ShivamJoker thank you! I appreciate the offer. I'm not familiar with AUR. I just skimmed their docs to gather some context so take the following with a grain of salt (and please do correct me if I'm wrong). As I understand it, goreleaser can publish the package but I'd have to registry myself/the project on AUR which means it's a little hard for you to contribute on this one? (I don't mean to push back, I love contributions, I'm only sharing a practical problem I see with this) |
Anyone can publish the package with permission but yeah, It would be better if you create an account and publish it. I can help with the aur script and testing. |
OK, thank you! I'll ping this issue when I've got something going so we can test it together 💪 |
Perfect thanks 🙌 |
@ShivamJoker I played around with this but completely forgot to get back to you 🤦 So the tl;dr is that the AUR packaging system is making it hard (for me) to register. Their captacha system assumes you have a running arch linux you can run command into but problem is I don't and made me wonder if I should commit to support something I cannot make work myself. In a way it's the same reason why I don't officially commit to support windows. I'm not familiar with the arch ecosystem. Maybe there's some middle-ground solution (like "brew taps" or something)? I have implemented the phone number generator (it's in main but did not cut a release yet. I will soon!) |
Ohh! I remember doing that while signing up, I could create an account on behalf of you or I could publish the aur myself and link to this repository. Also with brew it is possible because brew is also available on Linux. It will be good if you publish this in go as well, so people can use the That will work universally on any OS which supports Go. |
This is very kind of you! I'll reach out to you (via email) so we can talk about the details of this.
TIL!
This comment made me realise I never mentioned anywhere in the docs that's an option so I fixed that! ( |
I installed the package via ❯ go install github.com/lucapette/fakedata@latest
go: downloading github.com/lucapette/fakedata v1.4.0
go: downloading github.com/spf13/pflag v1.0.5
go: downloading github.com/gofrs/uuid v4.3.0+incompatible
go: downloading golang.org/x/text v0.3.8 |
@ShivamJoker it's in |
@ShivamJoker as I understand it, when there's a new version re-running the same command should update it. I'll ping you as soon as I cut the next release so we can test it? :) |
No no I mean if there is a go command which updates all the packages which we have installed. |
@ShivamJoker as far as I know there's no way to do that. I know it's been a few months but I don't seem to find the time to reach out to you so we can pair on this. It's still on my mind. I should have some time next week again (this week is already pretty wild) |
_pkgname=fakedata
pkgname=fakedata-bin
pkgver=1.5.0
pkgrel=1
pkgdesc='CLI utility for fake data generation'
arch=('x86_64')
url="https://github.com/lucapette/fakedata"
license=('MIT')
makedepends=('tar')
source=("${_pkgname}-${pkgver}.tar.gz::${url}/releases/download/v${pkgver}/fakedata_${pkgver}_linux_amd64.tar.gz")
sha512sums=('ebd8b62b292d0d2746c1f1caf1682a25f58f6eadc766c66fa464f310c0be4f7718670f07f31b216925cb3903b0386635582a004b6f5c12fe0645ae88ba5217c0')
package() {
install -Dm0755 -t "$pkgdir/usr/bin/" "$srcdir/fakedata"
} Hi @lucapette This is the PKGBUILD. Save this in a file named Do you want to publish and maintain it on AUR from your side? I could help you out with the same. If not, I'd happily maintain it on the AUR. flyingcakes |
It will be great to have this on AUR. I can give this a shot if you want.
The text was updated successfully, but these errors were encountered: