PortableActivate v3 - activate/deactivate portable applications
v3 announcement at viewtopic.php?p=45091#p45091.
********************Original message follows**************************
This is meant to be the 'sfs_load' for ".AppImage" v2 files and portable applications that are directories, like the @mikewalsh 'LAUNCH' collection.
After downloading a portable application, (and extracting if necessary), you run this utility and select the new application file/directory,
once it's "activated", the new application is available in the PATH and in the Puppy menu if it's a GUI.
## Uasge:
To "activate", run "PortableActivate", click on "Activate" and follow the dialogs.
After reboot, the portable application should still be integrated into Puppy.
When you no longer want to use the application, run "PortableActivate", select the appropriate file, then click on "Deactivate",
then delete the portable application file/directory.
PortableActivate, also has an "Executable" button, clicking this will produce a dialog to select a ".AppImage" file to make it executable.
This is there because a downloaded ".AppImage" file usually does not have "execute" permission set.
There is no need to do this if you "Activate" the ".AppImage" file.
## Download:
I've released PortableActivate as "AppImage" files at https://www.mediafire.com/folder/7fxgg1aygy6vi/portact.
Download 'PortableActivate-i386.tar' for 32 bit Puppies, or 'PortableActivate-x86_64.tar' for 64 bit Puppies.
Extracting the downloaded ".tar" file will produce a ".AppImage" file that has "execute" permission set.
So, download a PortableActivate ".tar" file, and extract it:
Code: Select all
tar xf PortableActivate-i386.tar
Then execute:
Code: Select all
PortableActivate-i386.AppImage
click on "Activate", and select the ".AppImage" file, thus "activating" the PortableActivate ".AppImage" file,
or
in a console, run:
Code: Select all
PortableActivate-i386.AppImage --appimage-extract
rename the "squashfs-root" directory to "PortableActivate", and "activate" that directory by executing 'PortableActivate-i386.AppImage',
or if you are running "ROX-filer" you can simply execute the "PortableActivate" directory, by clicking on it.
## How:
PortableActivate does this by creating a small number of files:
a symbolic link to the portable application somwhere in the PATH that gives it precedence,
if the portable application is GUI, it also creates:
an icon file in '/usr/share/pixmaps',
and a ".desktop" file in '/usr/share/applications',
in each case it will use a symbolic link if possible, otherwise it copies or generates a file.
Thus, PortableActivate has a small footprint in your "save", provided you store the portable application itself somewhere in '/mnt/home', outside the aufs stack.