| 1 |
On Mon, 15 Jun 2009 16:48:03 +0100 |
| 2 |
AllenJB <gentoo-lists@××××××××××.uk> wrote: |
| 3 |
|
| 4 |
> https://bugs.gentoo.org/show_bug.cgi?id=274197 |
| 5 |
> |
| 6 |
> The above bug brings up 2 issues: |
| 7 |
> |
| 8 |
> First, hplip says one thing, but does another with qt3 and qt4 |
| 9 |
> use-based dependencies. This is obviously a bug that needs to be |
| 10 |
> fixed. |
| 11 |
> |
| 12 |
> As a user, the second issue it brings up for me is what is the policy |
| 13 |
> applied to the rest of the tree with regards to packages that can use |
| 14 |
> one or more of several options (eg. qt3 or qt4) and have both / all |
| 15 |
> flags specified? |
| 16 |
> |
| 17 |
> Do packages that can use both/all always use both/all? |
| 18 |
|
| 19 |
Probably. |
| 20 |
|
| 21 |
> When both/all flags are specified, which one takes preferences? |
| 22 |
> Always the newer? |
| 23 |
|
| 24 |
When this issue arose up for www-client/opera because of upcoming Qt4 |
| 25 |
builds of (binary only) Opera, the qt team advised to only provide a qt3 |
| 26 |
USE flag and (thereby) make qt4 the default. So only if USE=qt3, then |
| 27 |
you get a Qt3 build of Opera[1]. |
| 28 |
|
| 29 |
Contrarily, net-print/hplip-3.9.4b appears to make Qt3 the default, |
| 30 |
while it could do entirely without IUSE=qt4, just like www-client/opera. |
| 31 |
|
| 32 |
|
| 33 |
Kind regards, |
| 34 |
jer |
| 35 |
|
| 36 |
|
| 37 |
[1] Technically speaking, you sometimes do get a Qt3 build in preview |
| 38 |
releases, but this shouldn't happen with stable releases of Opera. |
Archives