-
-
Save ruario/99522c94838d0680633c to your computer and use it in GitHub Desktop.
@ruario
I updated the spec file. Now rpm post scriptlet automatically creates symlink to libudev.so.1. Thanks for your good advice. I think your sh function is useful for installation for CentOS or Redhat variant in case of they don't know where libudev.so.0 is located at.
After I installed 'google-chrome-stable' package from Google, opera-developer detected pepper flash player plugin. It works on some websites including flash plugin contents.
Adobe Flash Player
Version: 14.0.0.125
disabled
Shockwave Flash 14.0 r0
Location: /opt/google/chrome/PepperFlash/libpepflashplayer.so
Type: PPAPI (out-of-process)
opera://plugins/
Now that the OpenSSL problems are gone, repackaging should be easier
I cant get either the fedora.spec file or the standalone installer in this threat to work with latest Opera developer.
With the standalone installer I get this:
./run: line 2: /home/SSamiK/opera-developer_25.0.1606.0_amd64/: Er en filkatalog
./run: line 2: exec: /home/SSamiK/opera-developer_25.0.1606.0_amd64/: cannot execute: Er en filkatalog
@SSamiK Most likely due to the change of name of the binary from opera to opera-developer. I have now fixed the standalone installer.
@nobuyuki-ito @Arilas @SSamiK @YeOK You do not need libssl libs from Ubuntu to get Opera working on fedora. A simple symlink will do. I have updated my instructions above and my own sample install scripts.
That SlackBuild from me is outdated. Please update the link to http://blog.t-rg.ws/uploads/opera.tar.gz or to my repo: https://github.com/fsLeg/SlackBuilds/tree/master/opera. The new SlackBuild can build both Developer and Beta flavors and can optionally build local version of FFmpeg.
On Fedora 20 and with Opera Beta 26.0.1656.27 I had to install libXss and make a symlink:
ln -sf /usr/lib64/libXss.so.1 /usr/local/lib64/opera-beta/lib/libXss.1
@fsLeg done. Thanks!
@RLndggr I checked and I did not need to do this with Opera 26.0.1656.32. Yes we depend on /usr/lib64/libXss.so.1 (provided by the libXScrnSaver package) but no compatibility symlink is required.
libXScrnSaver should already be present on a typical Fedora desktop install. However, if it is missing, you can simply issue the command:
yum install libXScrnSaver
FYI: I modified Fedora rpmbuild script to package opera for OpenSUSE.
@kikonen Thanks! I have added you above.
P.S. There is no need to do anything special for libssl on OpenSUSE ;)
Most of the rpm .spec files I have found use overly complicated workarounds for libcrypto (by bundling libs) and create rpms that will on work on specific distro releases by including libudev compatibility symlinks, rather than making them on the fly (as needed) in post install. I have therefore created some examples to demonstrate how I would deal with these issues.
@ ruario
I have Google Chrome Unstable installed. It looks like Opera only checks for the stable chrome directory when searching for pepper flash. A symlink added to '/opt/google/chrome' confirms PepperFlash is working.
Google use '/opt/google/chrome-beta' and '/opt/google/chrome-unstable'.