Home | Docs | Forums | Lists | Bugs | Planet | Store | GMN | Get Gentoo!

Full Text Bug Listing

I would like to add support to the www-client/opera ebuilds to denote whether
to use a version dynamically linked to a system qt3 or a system qt4. It would
appear the qt3 and qt4 USE flags cover this but I am not aware how other
ebuilds use these. Also, the qt[34]support USE flags appear to apply to qt
packages only, and not packages that depend on Qt, so those flags would seem
less appropriate. Please advise.

Do any package depend on opera, or would they need ot know which qt it was
linked against?

If you want my two cents on this, I would recommend forcing it to build against
Qt4 and offering a different package opera-qt3 for linking against Qt3. 
Otherwise, every package that has a depend on opera may potentially need to add
some kind of check as to which Qt its linked against as well.

No, nothing depends on Opera. Also, Opera is closed source, so upstream kindly
releases different builds that have been compiled and linked against different
Qt versions (3 and 4) and I could add some logic to the ebuilds that says that
USE=qt4 overrides USE=qt3, so that when both qt-3 and qt-4 are available, the
Opera build linked against Qt 4 is preferred.

Gotcha.

Certainly it up to you. In this case, using the qt3/qt4 flags are probably most
appropriate.  I was just thinking more along hte lines of libraries that link
against Qt which then have to be linked against by other programs - that is
much more difficult to manage dep wise if you don't know which qt it's linked
against :)

Thanks for the info. I would be able to simply use IUSE='qt3 qt4' then.

I want this resolved too. The additional use flag should be only "qt3" to
switch from using qt4, because the latest QT version should always be used.

(In reply to comment #5)
> I want this resolved too. The additional use flag should be only "qt3" to
> switch from using qt4, because the latest QT version should always be used.

The www-client/opera-9.51_pre2050 ebuild introduces the qt3-static USE flag.
The USE flag logic looks like this now:

# +qt-static +qt3-static = static-qt3
# +qt-static -qt3-static = (static-)qt4
# -qt-static -qt3-static = shared-qt3
# -qt-static +qt3-static = static-qt3

Please test and tell if you like it. I may then "backport" it to the 9.50
ebuild(s).

Created an attachment (id=158085) [details]
Port of ia32 use flag

I tried to port ia32 functionality from stable opera-9.50-r1 to snapshot ebuild
opera-9.51_pre2050.

I know that amd64 keyword is dropped intentionally and that there aren't any
amd64 builds in snapshot directory (so amd64 keyword is useless without ia32
use flag enabled).

I modified it for me to try qt4 static on my amd64 with ia32, but maybe it can
save some work, when new snapshot with amd64 builds exists.

(In reply to comment #6)
> (In reply to comment #5)
> > I want this resolved too. The additional use flag should be only "qt3" to
> > switch from using qt4, because the latest QT version should always be used.
> 
> The www-client/opera-9.51_pre2050 ebuild introduces the qt3-static USE flag.
> The USE flag logic looks like this now:
> 
> # +qt-static +qt3-static = static-qt3
> # +qt-static -qt3-static = (static-)qt4
> # -qt-static -qt3-static = shared-qt3
> # -qt-static +qt3-static = static-qt3
> 
> Please test and tell if you like it. I may then "backport" it to the 9.50
> ebuild(s).
> 

Thank you. I like it. Works as expected. Now there remains a question - where
is a version that is dynamically linked to qt4?

(In reply to comment #8)
> Now there remains a question - where is a version that is dynamically linked 
> to qt4?

Quite simple - Opera didn't release one. :)

(In reply to comment #9)
> (In reply to comment #8)
> > Now there remains a question - where is a version that is dynamically linked 
> > to qt4?
> 
> Quite simple - Opera didn't release one. :)
> 

When I use the combination +qt-static -qt3-static and set the Qt Native skin in
the configuration dialog, Opera still looks like it's using that default Qt3
style in the menus and save-file dialog. 

I'd really like it if I could get opera to use the Oxygen qt4 style.. is this
possible?

(In reply to comment #10)
> I'd really like it if I could get opera to use the Oxygen qt4 style.. is this
> possible?

Please don't tag support questions onto bugs that look similar. I suggest you
ask on a Qt forum.