You say Firefox 2.0, I’m sure you mean FF 4.0, no? Or 3.6? You can find these in the Mozilla repositories in the OBS, there’s no need to install from the tarball.
Just to add a bit more to your original question, .tar.gz files are not
really every installed in the sense you likely mean. Some files like RPMs
or PKGs are “installed” because the distribution has a system (a package
management system) to manage the packages. .tar.gz just means the data
are .tar’d and then gzip’d but the contents could be anything. Shipping
software in this way implies it will not be installed in a package
management system which is confusing if you want it “installed” in a way
native to the system, but nice if you want the single bundle of software
to work on more than one distribution (for example, on those that do not
support RPMs or PKG, etc.). Also not that .tar.gz or .tgz (same thing)
files will sometimes contain source code in which case the “installation”
involves compiling the software as well. The files could also contain any
other data not meant to be “installed”, which is why your question was
likely not easily answered via Google (because it isn’t really answerable
in any single way, and Mozilla probably has the best steps since this file
came from them).
Good luck.
On 11/07/2010 05:36 PM, chief sealth wrote:
>
> To extract the files from a tarball, use
>
> -tar -xvf archive.tar.gz-
>
> You say Firefox 2.0, I’m sure you mean FF 4.0, no? Or 3.6? You can find
> these in the Mozilla repositories in the OBS, there’s no need to install
> from the tarball.
>
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.15 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
Thanks for the replies. I am trying to run a script that works on Firefox 2.0, but not on any of the newer versions.
I ran it in OpenSUSE 10.1, several years ago, but cannot remember how I installed it, whether it was from a repository or installed in another way.
I was able to extract the file, which allowed me to see that there was a shell script installer within the package. It is now installed, but for future reference, what is the general method one would go about installing something from a .tar.gz file? you would abviously extract the file, but I know not all the packages come with a script installer, so how do you figure out where to go from there?
I was able to extract the file, which allowed me to see that there was a shell script installer within the package. It is now installed, but for future reference, what is the general method one would go about installing something from a .tar.gz file? you would abviously extract the file, but I know not all the packages come with a script installer, so how do you figure out where to go from there?
The tarball should contain a README and an INSTALL file. These will usually provide instructions. In the case of Firefox, as John says it is self-contained, and you should be able to run it immediately in the extracted directory.
The script I referenced apparently runs firefox, but does not install it. SO now I am sortof at a loss as to where to go from here. What sort of file should I be looking for to install the program? a .bin file?
No problem. I found both the shell script and a “firefox-bin” executable file, but the script merely runs the program, without installing it. I am unsure as to how to go about actually installing the program rather than just running it from the script. I am assuming the -bin file is the executable binary file, but have not figured out how to make that work.
you do not “install” the very old and dead firefox2
but if you insist on trying to use it on a version of suse that it was NEVER intended to run on
support for ff2 ended before suse 11 came out
IF ff2 some how dose work on suse 11.3 the install instructions are the SAME as they always have been!
copy the ff folder to /usr/lib and make all the needed links for the plugins ( current the current plugins( that ARE ALREADY installed) WILL NOT RUN on ff2)
for EX. the current flash plugin WILL NOT run in the old ff2
Really, the best solution would be to update the script to run on FF 3.6 or higher. FF 2 has security issues that will not be addressed, as it is no longer maintained. Don’t use it as your default Web browser.