Posts tagged with "TAR"
xzcat opera-11.60-1173.i386.linux.tar.xz | tar x(Replace "opera-11.60-1173.i386.linux.tar.xz" with the name of the actual Opera package you wish to extract).
If for some reason you are getting the packages directly from the Opera FTP server, downloading an Opera Next snapshot (development build) from the Desktop Team Blog, already have local copies of the packages or simply use a distro that is not listed and does not provide Opera directly within its repositories, here is a guide to help you match the package to your distro of choice, along with some installation instructions.
This blog post is primarily aimed at our intermediate to advanced UNIX users. If you are new to UNIX you may find this to be too much detail. However, if you are interested in packaging or just want to know a little bit more about what we changed behind the scenes read on! If you are a user of the install script bundled in the tarball packages, you should certainly read on as the changes are potentially biggest for you.
Completely uninstalling Opera 9.64, 10.00, 10.10, 10.11 and 10.20 when installed via one of our Linux tar packages
From time to time I get requests from users for help uninstalling Opera. Whilst we would obviously prefer you didn't do this , it can be a legitimate problem for users of our older tar packages and something I have written about briefly before. The difficulty is that although a list of files is echoed back during installation, we didn't used to provide any uninstaller with these packages.
Another reason you might want to uninstall Opera is that it is a sensible idea to remove old installs made by the Opera tar package install.sh script, prior to upgrading to more modern versions of Opera 10.51 and above. This avoids the potential for upgrade issues caused by our changed tar install procedure from this point onwards.
Below I will explain how you could manually remove a copy of the Opera Linux 9.64, 10.00, 10.10, 10.11 or the 10.20 desktop widgets labs release (and possibly older versions but I haven't checked) that was installed via the Opera supplied install.sh script.
Most of this information is now dated. Please read Selecting a Linux or FreeBSD package and installing it instead!
We frequently get questions about which Opera Linux package is the right one to install. Typically this is more common when we offer up a snapshot or when www.opera.com/download needs updating to show the latest and most popular distro version. My colleague csant has covered this topic before. However, as it is been a while and a few things have changed I think it is probably a good time for an update. I would also like to talk a little about the reasoning for the different packages and why we suggest one over another for a particular distro user.
Firstly for those who just want to know what to download and don't care too much about the background here is the quick summary:
- If you use a recent version of a modern popular Linux distro, you want one of the builds that includes 'gcc4' and 'qt3' in the name. (OpenSUSE 11.2 users should use a 'gcc4' 'qt4' .rpm package).
- Consider which processor architecture you use. We offer three for Linux: Intel (also called i386 or IA-32), x86_64 (amd64) and PowerPC (ppc). If this means nothing to you then you are almost certainly using Intel/i386!
- What package file format does your distro use? We offer two native types: RPM Package Manager (these end with a .rpm extention) and Debian Packages (these end with .deb). For users with another package management system we offer .tar files, optionally compressed with either the gzip or bzip2 compressors. I realise some people may still be unsure which package management system is native for them, so here are some example popular Linux distributions which would use each type:
.rpm = ALT Linux, CentOS, Fedora, Mandriva, PCLinuxOS, Red Hat, openSUSE & Yellow Dog
.deb = Debian, MEPIS, Linux Mint, Ubuntu & Xandros (Eee PC)
.tar = Arch, Gentoo, Sabayon & Slackware
So assuming you running a modern and up to date distro, on an Intel/i386 processor and need Debian packages you would want: opera_XX.XX.XXXX.gcc4.qt3_i386.deb (where the X's are the build and version numbers). Make sense? I hope so!
Note: I have assumed that FreeBSD and Solaris users are able to figure out which builds they need for their OS version. However, if you are not sure please do ask below as I would be happy to help!