I was wondering why Opera seems slower than it should be and I discovered that we are all using the static version. I asked some forum members whether they think we should switch to the shared version and some of them already have. I gather from looking at previous bug reports that a year or so ago, there used to be two separate opera and opera-static ebuilds. I think Qt version differences put the shared one out of action a while back but now it seems like things are okay so maybe it's time to bring the shared version back. I've modified the opera-7.23 ebuild to choose the static or shared version based on whether the static USE flag has been selected or not. It works for me though you may want to take a look over it yourselves. If this gets accepted, someone may want to modify the 7.50-Alpha ebuild as well... or I could I could do it! Let me know. Reproducible: Always Steps to Reproduce:
Created attachment 25026 [details] New ebuild for Opera 7.23 to handle shared and static versions
I wouldn't mind if we brought it back. I've personally just been making custom shared eBuilds for Opera with each release, and think that bringing back the shared officially is a good idea.
i added the shared version to alpha2 to test
That's great but the ebuild I made for 7.23 hasn't been added to Portage yet! I'm not supposed to do that, am I? I thought only you guys could do that.
sorry, forgot that one, also backported some other changes from the 7.50 ebuild (e.g. operanom2 useflag)
I'm testing the alpha2 ebuild on my system, and I can't get it to merge the shared version. I tried USE="static" emerge opera after unmasking it, and deleting the static file from /usr/portage/distfiles, but it still insists on downloading and installing the static version.
