I did that, but, it has a conflict with my paranoia-1.3.3.7-noarch-2.txz package.

This morning I have updated my slackware64-13.37 production servers:

openssl-0.9.8t: SlackBuild - source
Fixes:
- http://cve.mitre.org/cgi-bin/cvename...=CVE-2011-4108
- http://cve.mitre.org/cgi-bin/cvename...=CVE-2011-4576
- http://cve.mitre.org/cgi-bin/cvename...=CVE-2011-4577
- http://cve.mitre.org/cgi-bin/cvename...=CVE-2011-4577
- http://cve.mitre.org/cgi-bin/cvename...=CVE-2011-4619
- http://cve.mitre.org/cgi-bin/cvename...=CVE-2011-4109
- http://openssl.org/news/secadv_20120118.txt

php-5.3.9: SlackBuild (edited to change the VERSION number, you'll need also alpine's SlackBuild) - source
Fixes:
- http://cve.mitre.org/cgi-bin/cvename...=CVE-2011-4885
- http://cve.mitre.org/cgi-bin/cvename...=CVE-2011-3379

nothing broke so far.

Mozilla Firefox 9.0.1 builds without a problem using Pat's SlackBuild for 8.0.1. I added a link for the directory because there are a couple more files that you should place on the same directory of the SlackBuild. SlackBuild - Source

@bonixavier: It is even quicker to grab a binary of another browser. :P

Seriously though, if you have your heart set on Firefox, I wrote a quick script that checks for the latest version and compares with your own installed version. If yours is lower (well actually just different), it downloads the appropriate (for your architecture) binary package of Firefox and repackages it into Slackware package format. This is handy to me because even though I much prefer Opera, I like to have the latest Firefox for comparative testing. The script is here. Just download, make it executable and issue:

The advantages over Pat's SlackBuild are that it will work out the latest version for you, you don't need to be root to run it and a binary repack is a lot faster than a compile.

4 members found this post helpful.

Thanks ruario.

I just ran your script, and it works very well.

lol. I have Opera installed here and I like it very much. The address bar history search and the lack of a proper Noscript/Adblock combo are the only thing that keeps me from using it exclusively. On my Android I use Opera Mobile alone. But the main reason I brought Firefox up is because I understood that we'd be focusing on default Slackware packages.

There's also a repackaging script by Pat, but yours does more things. Thanks for that.


Edit: BTW, when building an Opera package using your script, KDE is always able to find the proper icons, which doesn't happen when running the installer.

Cant you just use the inbuilt "block content" and "edit site preferences" in place of those two? It does the job for me.

Not sure I understand what you mean about the address history though so I can't comment on that.

I mean the ability to quickly find a previously visited website by typing a few characters of its address or title in the address bar. In my experience, Opera does it well when you type the beginning of the addresses, but not so much when it's another part of the site address or when the title of the page you're looking for is not on its address. Opera is not terrible in this regard, it's just that Firefox does this much better. I hardly ever have to open the history on Firefox, but it's a more common thing to do in Opera.

1 members found this post helpful.

Ahh, yes, I understand what you mean now. Firefox does have the edge on that.

Opera? So I presume you are talking about my op2slk script and comparing this to the regular Opera install script? If so the difference is that the Opera install script defaults to different locations, either "~/.local" (for a single user install) or "/usr/local" (for a system wide install). My conversion script (op2slk) would make a package that sticks Opera directly in "/usr". So the difference is probably the fact that the icons are going in "install prefix/share/icons/hicolor" and KDE handles/caches them differently. I know that in Gnome for example, the very first icons placed in a new location are not picked up until you log out and log back in again. Which means that when people do an Opera single user install for the first time on a clean machine they have no icons initially. We get a lot of people mis-reporting that as a bug of ours even though there is nothing we can do about it.

Additionally we have extensions these days that can expand on the built in functionality.

Regarding the comments about the address bar and history. We are experimenting with changes to heuristics right now internally. So look out for those in a future release.

P.S. Now I don't want to encourage people to use other browsers but I am a realist and appreciate that some people will. Anyway I also have a latest-chrome script that works just like the Firefox one, which could be used by those that haven't yet seen the light and realised that Opera is the best browser! :P

If you are running -current like I am, you will have to first recompile libnotify and probably notify-python as well. I did both before ff-9.0.1 would compile on -current.

strange, I don't have to do that on slackware64-current: I've also built -and are running now- 10b5 and thunderbird 10b4.

but gotta say I used the build scripts in testing.

It had been compiling for almost 30 minutes when it died at "cannot find -lnotify". So I rebuilt both of those and started again with success.

I've been using the FF 9.0.1 packages from Salix on 13.37 with no problems:

http://slackware.org.uk/salix/i486/13.37/salix/xap/

http://slackware.org.uk/salix/x86_64/13.37/salix/xap/

I've used those repackages of FF in the past but then realised that I couldn't open a html in FF from the current working directory. Looking at the build script you can see why:

Should have just used a symlink, rather than a short shell script that switches back to the directory where the binary is actually located. This is one of the reasons I started to make my own.

To be totally fair, I haven't reported this yet. I must remember to do that tomorrow.