The new licq-1.3.4 ebuild uses flag "qt", but it is not described in profiles/use.desc and use.local.desc. I can found only qt3 and qt4. All old ebuilds are using "qt3" flag, so why the new licq ebuild uses "qt"?
s/qt/qt3/ thanks :)
you are welcome :-)
This is fixed(In reply to comment #0) > The new licq-1.3.4 ebuild uses flag "qt", but it is not described in > profiles/use.desc and use.local.desc. I can found only qt3 and qt4. All old > ebuilds are using "qt3" flag, so why the new licq ebuild uses "qt"? All of the licq ebuilds appear to use the qt3 USE flag.
(In reply to comment #3) > All of the licq ebuilds appear to use the qt3 USE flag. I synced with webrsync yesterday, so the snapshot was from the day before yesterday. I cannot sync now, but if it is already fixed, close the bug (or I will close it as soon as I sync/webrsync again).
(In reply to comment #3) > All of the licq ebuilds appear to use the qt3 USE flag. I have synced with `emerge --sync` just now, but `grep IUSE licq-1.3.4.ebuild` still gives me this result: IUSE="ssl socks5 qt kde ncurses crypt msn"
fixed in 1.3.4-r1, thanks for reporting.