Ruarí's thoughts

Subscribe to RSS feed

Posts tagged with "opera-next"

opera-next.SlackBuild (and opera.SlackBuild)

, , , ...

I know I have written about packaging way too much but I was recently asked for a traditional SlackBuild-style repackaging script for Opera Next. I already host Opera Next Slackware packages in my mini-repository. These are repackaged using my op2slk conversion script. The person asking however disapproved of how op2slk works because it does not use Slackware's makepkg (done so that I can repackage on a non-Slackware distros and so I do not need to use the root account).

Whilst in the majority of cases it is certainly preferable to use makepkg I do not agree that just because op2slk doesn't do so, that it is inherently bad or broken. I have been very careful to make sure it does many of the same things that makepkg does (i.e. It converts symlinks into shell script code in exactly the same format as makepkg, uses GNU tar version 1.13 style directory formatting for all entries within the tar package and makes sure all files are owned by root when packaged). That said, since it is relatively trivial to adjust the available opera.SlackBuild's to repackage Opera Next I decided to make one anyway. You will find it in my mini-repository.

At the same time I figured I might as well also created a opera.SlackBuild (see the Opera subdirectory). At least two opera.SlackBuild's already exist at SlackBuilds.org (Sbo) and Slacky.eu but I figured I'd do my own variant for fun. The differences from SBo version are: it is entirely self contained (no separate doinst.sh and slack-desc files); it uses the bz2 compressed tar package as a source rather than the xz compressed one (making it suitable for older Slackware versions); it will download the the "source" package if it is not present locally. The differences from the Slacky version are: it is self contained (no separate slack-desc); it uses the bz2 compressed tar package as a source rather than the rpms.


Edit: You can now also find an up to date opera-next.SlackBuild on the snapshot server itself! wink Click on the Linux/FreeBSD download link for the snapshot you are interested in and when the directory loads adjust the URL by adding .unsupported on the end. Or try this:

http://snapshot.opera.com/unix/latest/.unsupported/



P.S. Just because I made yet another opera.SlackBuild variant does not mean there is anything wrong with the Slacky.eu and SBo versions. There isn't! They are both well maintained and indeed mine borrows heavily from both of them. As much as anything I did it because I could and to provide another option. There is no particular reason to use mine if you are already happy with either of the Slacky.eu or SBo versions, or for that matter if you are using op2slk, my SalixOS SLKBUILD script or one of the binary packages I host! wink

If you are repackaging Opera for your distro, be careful not to over do the dependencies

, , , ...

I was recently looking around at Linux repositories that offer Opera and found one that listed kdelibs, qt, gtk+2, etc. as Opera dependencies. In fact Opera requires none of these to function!

Read more...

How to turn Opera Next into Opera and why you shouldn't do it

, , ,

The install script in our Opera Next tar packages includes a handy option called '--name' (which replaces our older '--suffix' option). It is provided so that you can install multiple copies of the same browser with different install suffixes. What do we mean by an install suffix? Well consider that Opera Next is for the most part just a suffixed install of Opera, with the suffix being 'next'. If you wanted to install a second copy of Opera with the suffix 'test', you would simply set this option as '--name opera-test'. Then you would have an 'Opera Test' install that used its own unique profile and sits alongside any 'Opera' or 'Opera Next' install you already have present.

This is obviously a pretty cool and powerful feature for testing but what some might find particularly interesting is that you could use the '--name' option to turn Opera Next into Opera. wink

Now before I tell you how you could do this let me first say that you shouldn't bother doing this! There really is no good reason to do so. If you think there is, think again.

Read more...

Opera 11.11 for Slackware

, , , ...

Edit: This post is old, get 11.51 instead.

I just noticed that (as I write this) the Opera SlackBuild is a little old, since it still points to Opera 11.01 [Edit:It has been updated now!], whilst we have released Opera 11.10 and today 11.11 (which includes an important security fix). I'll see if there is something I can do to get this updated. In the mean time Slackware users can use my op2slk script (more info on op2slk here) to convert one of the Opera tar packages into Slackware native format.

Read more...

Automatic conversion of Opera and Opera Next tar packages into Slackware format

, , , ...

The last time I wrote about distros and packaging I provided a couple of example Slkbuild scripts for conversion of Opera packages into Slackware format. At the time I debated maintaining these scripts and updating them as future versions of Opera where released in much the same way I do for the Arch Linux PKGBUILD scripts (also mentioned previously). However I have since realised there is an easier way! wink

Read more...