Sloan wrote:
Aaron Kulkis wrote:
I use suse packages whenever available, but out of curiosity, how does installing an unmanaged tarball help? I just download and ungzip/untar in /local, run the installer script and install in /opt.
Right, you can do that, but how does it help?
Standard Mozilla installations don't throw files all over the directory tree ... the whole thing installs into one directory (and its sub-directories) wherever you tell the installer to put it. For me, each version is installed into it's own directory in /opt. I had /opt/sea-monkey1.1.{5,6,7}. When 1.1.8 came out with a security fix, I just deleted the 1.1.5, 1.1.6, and 1.1.7 directories, and the install tar.gz files. Uninstalling them was as simple as this: rm -rf /opt/seamonkey1.1.{5,6,7} rm -rf /local/downlaod/*seamonkey*1.1.{5,6,7}*
I really don't give a hoot about the browser RPM's, other than having something to go to the Mozilla website to IMMEDIATELY download the latest release.
I'm curious why you use suse - wouldn't LFS or Rock Linux be more to your liking?
I'm happy with SuSE. Until now, I didn't know about LFS or Rock Linux...and frankly, don't care about them. The reason I update Mozilla so much is because it's a piece of very rapidly improving software, and keeping track of the versions doesn't need redhat package manager or any other sort of similar package/software management, because the Mozilla people do things the Right Way(tm) for installation to /usr/local or /opt.
Joe
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org