Request for Arch User Repository (AUR) Package

[Arthur-Stuhl]

• [x] I have searched the issues list for this, and I couldn't find it.

Dear Social Stream Ninja Developer(s),

I am a user of Social Stream Ninja and would greatly appreciate if was possible that you would consider creating a package for the Arch User Repository (AUR). This would simplify installation and updates for users of Arch Linux and its derivatives, such as Manjaro.

I'm not currently planning to create a package myself, but believe an official AUR package would be a significant benefit to the Arch Linux community and make Social Stream Ninja even more accessible.

Thank you for your time and consideration.

[steveseguin]

https://aur.archlinux.org/packages/socialstreamninja

Thank you for the request.

I have NOT tested this, as I do not use Arch linux, but please feel free to fix things as needed here: https://github.com/steveseguin/ssn_app/tree/main/aur

I can push new updates on request.

[Arthur-Stuhl]

Dear Stevesguin,

I just tested the PKGBUILD you provided but it seems to fail to install with the following error. That the URLs you put aren't valid for the appimage and .desktop file.

[Arthur-Stuhl]

Alright I got the PKGBUILD working but you may or may not still need to edit some stuff see updated file here.

https://github.com/Arthur-Stuhl/ssn_app/blob/main/aur/PKGBUILD

[Arthur-Stuhl]

Please consider utilizing Electron to build the package from source on the user's system in your PKGBUILD. This approach allows you to leverage the system-wide Electron, enabling the use of newer versions and enhancing transparency.

When building your package, it's important to clarify that you should use Electron as provided by the system's package manager, rather than the version that comes from npm.

Using the system-wide Electron ensures that your package can take advantage of the latest updates and features available in newer versions. This approach also promotes better transparency, as users can see and manage the Electron version installed on their system.

In your PKGBUILD, specify the dependency on the system's Electron package. This way, when users install your package, it will automatically use the Electron version that is already installed on their system, rather than bundling a potentially outdated version from npm. This not only simplifies the installation process but also aligns your package with the user's environment, leading to a more consistent experience and less duplication of packages. Because if it's already there why not use it instead of downloading it again and having twice of the same thing?

P.S. Please consider updating the version number in the PKGBUILD in the AUR.