I downloaded and saved "seamonkey-2.46.tar.bz2" to /home/user/.local
Then extracted the contents like this:
Code:
tar -xvf seamonkey-2.46.tar.bz2
as my normal user. It should leave a single "seamonkey" directory (/home/user/.local/seamonkey).
That's important so it can update itself with permissions to write to its own directory.
Now comes the softlink which allows you to launch it from the terminal, or from dmenu, etc.
Next,
as root:
Code:
ln -s /home/user/.local/seamonkey/seamonkey /usr/bin/firefoxseamonkey
Now this will run just fine. Although Slackware (slackpkg) won't "know" it's installed, there is really nothing wrong with running software this way.
The only caveat I know of is this: a couple years back, the (then) new version of Seamonkey would not run on 14.1 because it had an older version of glibc than the new Seamonkey required. So I had to wait for Slackware to update. So you might run into blips like that. If you go this route, it's a good idea to put the word seamonkey into slackpkg's blacklist file: /etc/slackpkg/blacklist
By no means am I a guru, I have just played with this stuff long enough to get done what I want to get done. Namely, having a system set up MY way.
Thank you Patrick and all who support Slackware!