Bug 508 – Opera portage: statically vs. dynamically linked QT

• Product: Gentoo Linux
• Status: RESOLVED FIXED

[Description Arcady Genkin 2002-02-03 01:21:54 UTC]

The opera portage installs with QT 3, but doesn't work with it.  The reason 
being that the Opera portage installs the version, dynamically linked against 
QT 2.  Opera provides a statically linked package as well, which would work 
with any QT, and without QT installed.  Maybe it's a good idea to switch the 
portage to the statically linked opera?

[Comment 1 Dan Armak (RETIRED) 2002-02-03 14:59:05 UTC]

As I understand, the opera we curently have works with the qt 2.x we 
currently have (x11-libs/qt-2.3.1-r?). So we just need to fix the opera 
depend on qt so that qt2 is emerged, and it will work. Please correct me if 
I'm wrong; I'm fixing the opera ebuild now.

[Comment 2 Arcady Genkin 2002-02-03 15:42:53 UTC]

Yes, that's it, I guess.  ">=x11-libs/qt-2.3.0" was not good.

But, perhaps, we could also have an opera-static portage, which would not 
require qt libraries.  The current ebuild can be trivially modified to work 
for the static opera distribution, ustt by changing the archive name (IIRC, 
s/2-shared/1-static/).

[Comment 3 Dan Armak (RETIRED) 2002-02-04 12:52:01 UTC]

How would a static package be better than a dynamic one? Whe would you choose to use a static one (except to save the qt compiling time)?