AUR package

[gempir]

This is totally a nice to have and a low priority thing but an AUR package could make it easier for linux users to install Bruno.

https://aur.archlinux.org/

https://wiki.archlinux.org/title/AUR_submission_guidelines

[robertoszek]

I created a PKGBUILD and submitted an AUR package using the AppImage:

bruno-appimage

@helloanoop or any other contributor, feel free to take ownership or become a maintainer if you want to.

[helloanoop]

Thanks for this @robertoszek ! Will take a look at this shortly

[vbouchaud]

Hi there I took the liberty to create PKGBUILDs for the Arch User Repository before I saw @robertoszek's bruno-appimage (which is currently flagged as out-of-date). As customary for the AUR, I created three alternative packages:

• bruno-bin, basically extracting the deb file you release and using its assets directly in the produced archlinux package
• bruno, a PKGBUILD trying to use Archlinux best practices for electron/nodejs related packages. This one will build using the system's electron instead of one it would have to download, and will not contain an embedded electron, only the asar file.
• bruno-git, same as the previous bruno package but using this repository's main branch as sources instead of the latest tag.

Please note that for those last two, I use nvm to build with the given node version and I fixed the electron dependency to electron21 (21.4.4 is the one currently shipped by archlinux) which is the closest (as of today) from the one used (21.1.1) in bruno-electron/electron-builder-config.js.

AUR packages are, at the end of the day, still opinionated user produced content that might not reflect the will of the developers from the original project. Feel free to tell me if you see any way to improve them. Also, for anyone wanting to improve them, pull requests are welcome here.

[DeJayDev]

Hi,

I've also created bruno-electron as a fork which has chosen to drop nvm and properly depend on electron for users who may already use system electron bundled apps like discord_arch_electron or discord-canary-electron-bin.

As mentioned by @vbouchaud, AUR packages are opinionated user produced content. So not everyone may agree with my decisions here either.

I've chosen to remove nvm in favor of a Node v18 or higher version check. Removing nvm drops the dependency on yarn allowing the package to be installed without using --assume-installed (ie: paru --assume-installed yarn bruno). I'm a lot newer at maintaining PKGBUILDs but did still want to provide a smoother install experience. I'd be also happy to provide a bruno-electron-git

[DeJayDev]

In response to the recently added publishing.md, I would like to know how you'd like bruno-electron to continue. I'm sure @vbouchaud will also need you here.

Please advise @helloanoop, I personally will keep bruno-electron at v0.25.0 until then.

[helloanoop]

Hey @DeJayDev Thank you for getting in touch 💛

I understand that unlike other operating systems, Arch is a unique case, offering significantly more flexibility when it comes to configuring various aspects.

I'll comeback to this in 2 weeks, until then you can continue things as is.

Here is my rough plan

1. I'd like to assume ownership over the main bruno package in AUR cc @vbouchaud
2. Explicit permission will be granted to maintain and publish certain builds under bruno-* for some maintainers in AUR community.

@DeJayDev please continue maintaining your bruno-electron package by updating it with new versions. We can connect back on this in 2 weeks time (where I will put your package up on the site download page mentioning the grant of explicit permission to maintain your version). I am bit occupied this week with upcoming 1.0.0 release activities.

[vbouchaud]

Hi @helloanoop No problem, let me know which AUR username I should give ownership to.