(old)Puppy Linux Discussion Forum

sunburnt wrote:Tman; SFS files could have and use the same cleanup script more or less.

I am afraid it is not that simple. We would need an sfs-loader that handles pinstall.sh and puninstall.sh scripts or a similiar type of feature for that to happen.

gulk wrote:@darkstrike,

please start firefox from a console; I think I had the issue you mentioned and it was coming from a incompatible https library. Once I fixed that, the problem went away. I don't remember exactly what I fixed, but if you give me the error message from your console, it might ring a bell.

Sure Gulk,

I've been tinkering with Linux for a few years now, but me and the console aren't terribly well-acquainted as of yet....I should be able to start it with just the command "firefox" correct? (At least I know I've done that before.)

Is there a certain command to use to show the error messages?

Tman; Your right of course, I was thinking manually run uninstall.

How about the idea of Squash file apps. that mount but don`t union?
I have a loader for them, on startup it makes a menu of all SQ apps. found.
Apps. are only mounted when run, and they`re unmounted at exit.

So NO install, little Save space taken, and NO union layers used...

Tman; I started making an SFS file from your Firefox-11 package.
Upon looking at it, I wondered about a few things...

In /usr/bin is firefox_setup which wipes out the existing Firefox.
Can`t 2 Firefox versions exist together?
Especially because your Firefox-11 package is in /opt .
But all the system files and Firefox config. files are common.

# So then shouldn`t the files in an SFS just coverup the old Firefox files?
# Except for any config. files that are on the Save top layer of course.

Each app. version should be written to exist in a sandbox ( of course...).
It`s hard to believe the Mozilla people can`t do any better than that.

And all apps. when run should create any non-existing config. files.
The apps. are more reliable, and no need to copy SFS config. files.
Just prefix the config. file names with the apps. name
( firefox-11.bookmarks.html ), then they are easily removed.

Hi Sunburnt,

I packaged the Firefox pets in a more complicated manner in order to add extra functionality AND to have thse extra functions in the sfs.
It was tricky because sfs files do not overwrite over the original files in the main sfs.

For example, say you have /usr/share/applications/firefox.desktop and /usr/local/bin/defaultbrowser in the the main sfs...even if you delete those files, they will still be in the main sfs (unless you remaster) and the firefox.sfs cannot overwrite those existing files.

That is why I had to create unique folder names and have the firefox .desktop file run a script instead of the actual binary. Using a script was the only way I could get the sfs to delete old firefox files and folders, so that the sfs would work the way I want it.

I put firefox in the /opt folder, but the firefox_setup script will remove any existing /usr/lib/firefox folder and make a symlink to the /opt/firefox folder.

I could have made the pet simpler by just making a standard firefox pet and adding pinstall and puninstall scripts to add the extra functions that I wanted, but if you were to convert such a pet into sfs format, the sfs would not work as expected. My solution ended up to be quite tricky and took me at least 5 tries, but I couldn't think of a simpler way.

the extra functions include:
- removing old firefox folders
- asking to make firefox the defaultbrowser
- asking to remove old firefox saved settings
- adding custom saved settings
- doing cleanup on uninstall of firefox (works in the pet only due to puninstall.sh options not available in sfs)

- I guess one could go about installing 2 versions of firefox, but I see that as extra bloat, and would only choose the one that works best for my system

** there is a problem with the sfs, which is why I only uploaded the pet for firefox-11...when you load and unload the sfs multiple times, some files no longer get removed and overwritten properly. I have not managed to solve this problem. When you load it only once, everything should work as expected.
If you wanted to clean up the files when unloading the sfs, you could copy the puninstall.sh from the pet and name to something like /root/my-appications/bin/cleanup_firefox.sh
-

Hey Tman; I agree that only one good Firefox is needed. The newest hopefully.
Firefox use to be the best browser, but it`s gotten worse and worse.
I don`t know if it`s Mozilla`s fault or the folks building the packages.

Sounds like added SFS files go underneath the main SFS files in the union stack.
Otherwise an SFS`s file`s would over shadow any existing duplicate files.
This keeps Puppy safer, but it makes SFS files less than they could be...

This is part of why I dislike union file systems. Buggy, complex, and unneeded.

I`m going to try to make a no-union version of your Firefox-11.
I need to know the compile path to use as the Squash file`s mount point.

### Q... What was the exact "complete path" you used for compiling Firefox-11 ?

sunburnt wrote: Sounds like added SFS files go underneath the main SFS files in the union stack.
Otherwise an SFS`s file`s would over shadow any existing duplicate files.

Yes, that is the way sfs files are configured in Puppy. You have to modify the initrd file if you want to alter this. That is what Jemimah has done for her adrive.sfs in Saluki.

### Q... What was the exact "complete path" you used for compiling Firefox-11 ?

These are Firefox official versions, meaning the binaries and libs have already been compiled by the folks at mozilla.

Just now Mozilla has three patched official firefox releases: 3.6.28, 10esr and 11.0. Mozilla has abandoned all other versions of firefox, they are unpatched and unsupported.

Support for Firefox 3.6 is planned to end on 24 April 2012. So, there is three weeks for 3.6.28.

Extended Support Release (ESR) releases will be maintained for approximately one year, with point releases containing security updates coinciding with regular Firefox releases. ESR is for groups (is puppy users such a group?) who need extended support for mass deployments: http://www.mozilla.org/en-US/firefox/organizations/faq/.

Firefox 11.0 is current stable release, released on March 13, 2012. Planned release date for firefox 12 is 24 April 2012. And so on with cycles of six weeks.

Is there any point to invest in ESR?

Yes, in fact could I request that of you compilers please?
The 3.6.x series that is. Latest is 3.6.28 as mentioned.

Certainly under smelly old Windows these ones are lighter on memory (and cpu) usage than the versions from 4 to 11. There have been lots of complaints about hogging and leaks. Not sure if this is the case under Puppy, might be worth doing some tests.

OscarTalks wrote:Yes, in fact could I request that of you compilers please?
The 3.6.x series that is. Latest is 3.6.28 as mentioned.

Billtoo has already compiled Firefox 3.6.27. His thread for it is here -> http://murga-linux.com/puppy/viewtopic.php?t=74341

For those who want to compile Firefox themselves, please see the following thread: http://www.murga-linux.com/puppy/viewto ... 792#621792

**be warned: It froze up for me after about 2 hours of compiling on a Pentium4. I was only successfull when I tried it on my AMD dual-core.
-

Although, Firefox-11.0 runs very well for me; for those who want the latest:
Firefox-12.0 is now availiable.

Hi folks,

Firefox-13.0-official.pet is now available.
Following Semme's advice, here are the Release Notes.

Tman wrote:Firefox-13.0-official.pet is now available.
Following Semme's advice, here are the Release Notes.

Does this work in Lucid Puppy? I don't want to go to the hassle of upgrading to a newer Puppy just yet.

If it doesn't work with Lucid, what's the latest Firefox pet version that will work with it?

Thanks!

silverojo wrote:

Tman wrote:Firefox-13.0-official.pet is now available.
Following Semme's advice, here are the Release Notes.

Does this work in Lucid Puppy? I don't want to go to the hassle of upgrading to a newer Puppy just yet.

If it doesn't work with Lucid, what's the latest Firefox pet version that will work with it?

Thanks!

Yes it does work in Lucid.

Enjoy

Bones

Firefox-13.0 has now been replaced with Firefox-13.0.1

It inlcudes a bugfix for flashplayer.
http://www.mozilla.org/en-US/firefox/13 ... easenotes/

Firefox 13.0.1 ( English,GB ) - Lucid 528-005

Download:

http://www.datafilehost.com/download-a42c1fa1.html

Firefox-14.0.1-official.pet has just been uploaded to my little repository. To download, see the the first post of this thread. Versions 8 and 13 have been removed.

What's New:
http://www.mozilla.org/en-US/firefox/14 ... easenotes/

I'm saving some language packs for Firefox/IceCat here:

https://www.dropbox.com/sh/a2n6emd3t3olh0x/Hjy8Bod_ta

This is convenient because not everyone can compile separate versions for their languages, or the person who maintains the packages doesn't have enough time to do so. This is also convenient because at times updates for Puppy Linux aren't done as soon as a new version of the browser is released, and sometimes these langpacks disappear or are blocked for other browsers.

I'm saving some language packs for Firefox/IceCat

vicmz, I've placed a link for them on the first page, so they will be easier to find later on.