UPDATE FROM MABULA
I have had a very rough 2 months unfortunately health wise. I was struck 3x in a row with bacterial infections. The second infection occurred  after a routine hospital checkup and I became very sick. I had to rest and take a lot of antibiotics. Once I was recovering and restarting work 1 month ago, I again became sick. The infection was not yet gone, so even more antibiotics and rest was needed. Needless to say, it took a lot of my energy and I needed a lot of rest.
Finally, the infection is really gone and my energy is coming back step-by-step now and I have started work again. I am terribly sorry to have kept you waiting for support. I will address all outstanding questions and e-mails step-by step and will be on the forum daily from today.
APP 2.0.0-beta47 will come soon as well, a lot of work was already completed before I became very ill, so the release is also nearly ready for you. Beta47 will be much faster actually. Many workflows will be more than 2x faster, mosaics can even be 10x faster than before because registration really received a major boost... all compared to beta46. Â Before I release it, I will make sure that everything is working properly and then I will release it.
Hi,
I am using Arch Linux distribution, and it does not use deb or rpm package. There are some tricks to install deb/rpm package on Arch, but those are not recommended. Nevertheless, I have tried (using dpkg) but APP crashes on launch.
Is there an other way to install it ?
Â
Â
Thank you ! 🙂
Good question, not sure about that and we asked Mabula to have a look. He's very busy on trying to release the next version atm, so if you don't get an answer within a week or 2, please remind us. 🙂
Thank you Vincent! 🙂
@vincent-mod hi, any news about an install on arch ? thanks ! 🙂
@thibautflt We asked Mabula and there currently is no way to install APP other than via the deb or rpm package. Also, there are no plans to enable this at this moment, sorry.
I use Arch Linux. I install APP by downloading the .rpm package and extracting it. You will then have a folder labeled opt. Open the opt folder there is only a folder labeled AstroPixelProcessor. Copy this folder to /opt on your computer. That is all there is to it. You can then run the program using the command /opt/AstroPixelProcessor/AstroPixelProcessor.
[...] You can then run the program using the command /opt/AstroPixelProcessor/AstroPixelProcessor.
You can also copy /opt/AstroPixelProcessor/AstroPixelProcessor.desktop to e.g. ~/.local/share/applications/ so APP will show up in your menu.
EndeavourOS user here. Thank you for this!
Hi all, @astronikko @the1batman @msa
So besides the RPM and DEB installer for linux, what is the other needed installer type then? Would APP Image : https://appimage.org/ work in your Linux distributions? I should now be able to add support for that 😉
Mabula
Possibly. I think Flatpak is more common for multiple distributions. I was thinking about putting together a package for the AUR (Arch User Repository) that uses the RPM package.
I'd prefer a package that can be updated along with all other system packages using pacman, or an AUR helper like paru. I haven't published any packages myself, and my understanding of them is still only rudimentary. My only concern with Flatpak or Appimage is if APP will take a performance hit due to how it's packaged.
For the RPM, I basically expand the archive and copy the contents to the root file structure:
rsync -avh --progress [source]/ /
Where [source] is the path to the expanded RPM package. It copies the contents of the ./opt and ./usr contained within to the root file system /opt and /usr directories, while preserving symbolic links.
@mabula-admin Howdy - I ended up switching to a fedora variant (Nobara) and it works fantastic there. But to answer the question an appimage or a flatpak are both fantastic choices. I can install or use both of those with no issues.
Hi @astronikko & @the1batman
Okay, thank you very much for the feedback.
Flatpak or AppImage will not affect APP's performance, I am sure about that 😉 And extracting form the RPM package is fine as well with above instructions.
The way that we make our RPM and DEB packages is to use a third party packager. This 3rd party now supports AppImage, so it should not prove difficult to add that to our Linux packages. Flatpak is not yet supported unfortunately but might be supported as well going forward by this third party provider.
AppImage is very simple and should work on basically all Linux distributions I think.
Mabula
Sounds good! Appreciate the insight into the packaging process, too. Thank you.
@astronikko you are most welcome !
I will try to change our build process to include the AppImage for Linux starting with 2.0.0-beta36 😉
Mabula
