AppMan as an AppImage?
probonopd opened this issue · 5 comments
Hi, I'm planning to made an AppImage for it in the future, but being a bash script that contains all the instructions for each app of this repository (that for the moment are less than 40) I should improve it before, and finding a way to merge the istructions for each app (about, remove and install). Pratically AppMan must become completelly independent from the name of each programm (for all the aliases, for example firefox-stable|firefox, freeCAD-mamba|freecad|freeCAD, google-chrome|chrome, etcetera...). Until then, I must add new lines to the main script.
Thank you very much. Looking forward to it! 👍
Hi again, AppMan now is ready, but being a script that calls other scripts into a /opt/bin folder to be created and being many script depending on your tools (pkg2appimage, appimagetool and appimageupdatetool) as described in the installation guide, creating an AppImage for it seems to be useless.
All I suggest now is to create recipes using my scripts. As you can read from them, they are a mix between your pkg2appimage recipes with the support of appimagetool. The final result is an AppImage in /opt/bin with icon and launcher in the menu.
This is just an hobby for me, I'm not a real expert or a developer, but AppImages have fashinated me. They made me think that we can really try to merge all the linux distributions and stop fighting each other for Debian or Arch. Is this continuous division that takes linux longer from the masses. Maybe using standalone apps (and a centralizate repository) we can really made the difference. But I think AppMan should remain a script.
Sorry for my long talking, but for me is an honor to be contacted by the father of standalone apps on linux. I wanted to take this opportunity to thank you.
Thanks @ivan-hc, added it to https://github.com/AppImage/awesome-appimage#package-managers.
hi, I've just created an AppImage for AppMan (x86_64)