#Firefox esr 24 portable how to
#Firefox esr 24 portable update
#Firefox esr 24 portable portable
#Firefox esr 24 portable windows

Your 'portable' method I think would be more valuable if it was inside a mountable disk image container, using something like Veracrypt or LUKS. This 'portable' method does have merit for 'roaming' user data via USB stick sneaker nets. Now back to the postives of the 'portable' method. It's easy to load/unload SFS files, AppImages, etc. which have features that work better in older/newer versions. Finally, sometimes I have different versions of VirtualBox, LibreOffice, Blender, etc. Applications might bebacked up with data, which can increase the backup size hundreds of MB. If there are many 'portable' apps loaded, doing user data backups can be difficult. Also, having an app like Firefox or Blender in a SFS file can save hundreds of MB. That way I can use Puppy's savefile encryption, and not need to worry about defining data/config paths for each application. It is the friendly Puppy way.Īs for me, I prefer having profile data separate from the application. I can see the benefits of this set up in certain circumstances.īefore I continue, I just want to say that my reply is only for inspiration, not to criticize in any way. You are sym linking apps and libs into Puppy's system paths. Enjoy!Īh, now I understand your definition of 'portable'. Just navigate through, and help yourselves to the one you want.

#Firefox esr 24 portable update

These should still update themselves as normal, using the built-in Firefox update mechanism.īoth 'mainline' Quantun, and ESR (Extended Support Release) versions are available, in both 32-bit and 64-bit varieties:-įor anyone who's interested, they can all be found here:. With the 'extralibs' directory - for the PulseAudio emulation stuff - also now living at the top 'level', nothing extraneous remains within the firefox directory. When the add/remove scripts are used, 'fixmenus' runs, followed by 'jwm -restart'.same as Puppy does when installing packages (which doesn't close anything you may have open.)įred's 'ff' script and my 'LAUNCH' script have been combined, along with now creating the 'profile' directory at the top 'level.

#Firefox esr 24 portable how to

MenuAdd & MenuRemove scripts are self-explanatory, and the 'MenuReadMe' explains how to use them effectively.

#Firefox esr 24 portable portable

Since then, I've also added the ability to add a Menu entry from wherever the portable directory has been located. He was absolutely delighted with it, and I retained the concept, because I thought it was a better layout. Hence the 'LAUNCH' script.and by placing the entire thing on a suitably-formatted flash drive, it was totally portable, and he could plug it in & use it anywhere he wanted. (He admitted he wasn't very good with Linux, and he was so nice - and very polite with it - that I did what I could to make it easier for him). So I used the then current Firefox ESR, basically using Fred's layout, but with the clearly labelled 'LAUNCH' script at the top 'level', pointing to the 'ff' script inside. My use of the 'LAUNCH' script first came about through helping a sweet old guy over at BleepingComputer, who'd made the switch to Puppy and wanted to have a 'shared' browser he could use with more than one Puppy/machine. That original release of Fred's 'showed the way', as it were, and set me on a path which still has no end in sight.

#Firefox esr 24 portable windows

It was a concept I'd encountered years before in Windows XP, and one which I'd always wanted to get working in Puppy. This kept everything together in one place, and allowed the entire browser directory to be moved from one location to another.hence, it became 'portable', no longer being tethered to a fixed, 'standard' location. That script made use of the Firefox ability to specify the location of its profile directory, so Fred used this to create the Firefox profile inside the 'firefox' directory. This is a further 're-work' of Fred's original FF-portable.įred's original simply placed a short script, called 'ff', inside the firefox directory. So I've 're-jigged', & built some new versions in my now 'standard' portable layout. It struck me last night, it's been a while since I created any updated packages for these.