I've discovered a bug within what I think is PAI - When running the installer against an app destined to be installed in CommonFiles, if there is both an appinfo and a plugininstaller file, the appinfo is given precedence, and the app is pacakged to install to PortableApps. However, if the appinfo file is removed/renamed, the plugininstaller is given precedence as expected. The issue arises wherein appinfo.ini is required by a launcher running from CommonFiles.
Accordingly, it is currently impossible to install a PAL-based app to CommonFiles
(Yes, I'm aware the PAL launcher will be unnecessary once PAL 2.3 and PAF are updated)
Any thoughts on how to fix this?
Visit the Community page
Join our forums
Subscribe to our email newsletter
Subscribe with RSS
Follow us on Facebook
Follow us on LinkedIn
Follow us on Twitter
Follow us on Mastodon
Follow us on BlueSky
The short answer is, you're doing it wrong. CommonFiles is for libraries only. No launchers. If something needs its own launcher, then it's not a library for other apps to use, it's an app. And apps don't go in CommonFiles, they go in PortableApps. Think NSIS Portable and the way it is used by PAL.
Sometimes, the impossible can become possible, if you're awesome!
It's a temporary fix for Ghostscript until Chris pushes PAL 2.3 and Ghostscript is in PAF, as the settings made by the Ghostscript launcher will be made by PAL instead. So for now should Ghostscript continue to be installed to PortableApps?
I mean if it's in common files it should not have a launcher. If it has a launcher it can NOT go in common files.
Sometimes, the impossible can become possible, if you're awesome!
makes sense. Now that I think about it, I think I've been a bit short-sighted with how I personally have been using Ghostscript - I just realized I can accomplish the exact same results I need in Scribus' launcher.ini, easier, resulting in no need for a launcher within Ghostscript itself.