Create a AUR package about beatconnect_client HOT 3 OPEN

I have some experience with the AUR, but zero with building a beatconnect release. Can you give me a list of steps or something like that?

Also, do you want control over the AUR package, or just a AUR package?

from beatconnect_client.

Hi

Beatconnect client is running with https://www.electronjs.org/ so I think the procedure might be a bit different.
This link might help https://wiki.archlinux.org/title/Electron_package_guidelines.
Also, I added more information in README about building the app, although I don't think it will apply in the case of AUR. Except for the env vars that will still be needed, but I can provide you the production env variables if needed.

I never used AUR but I know some of our users do. What's the difference between having control over it or no? As long as I can update it easily on each new release that good.

And thank you for willing to help us on Beatconnect, I really appreciate it. If you need anything we can discuss on discord if you want: YadPe#9011

from beatconnect_client.

Hi

Beatconnect client is running with electronjs.org so I think the procedure might be a bit different.
This link might help wiki.archlinux.org/title/Electron_package_guidelines.
Also, I added more information in README about building the app, although I don't think it will apply in the case of AUR. Except for the env vars that will still be needed, but I can provide you the production env variables if needed.

That's difficult. AUR packages are just instructions on how to build something on the user's machine, so in order for a user to be able to build beatconnect, you'd need to deliver that token to users in cleartext.

There's also another type of package, suffixed with -bin. Instead of building on the user's machine, they just download the release (for example, the .deb file) and create a package from that. That seems to be a better way here.

I never used AUR but I know some of our users do. What's the difference between having control over it or no? As long as I can update it easily on each new release that good.

It comes down to who is able to update it. You cannot update an AUR package without being able to build & test it, i.e. you have to have arch or a derivative running. The alternative is to have it maintained by third parties, so somebody (me) would have to react to every beatconnect release by updating the AUR package.

And thank you for willing to help us on Beatconnect, I really appreciate it. If you need anything we can discuss on discord if you want: YadPe#9011

I'm on the discord already, I just don't have time for more than a comment in passing right now. Hopefully in a few hours.

from beatconnect_client.