| 1 |
Kevin F. Quinn wrote: |
| 2 |
> Problems with having 'qt' to mean latest and 'qt3' as specifically |
| 3 |
> version 3 include: |
| 4 |
> |
| 5 |
> 1) Target package depends on build system (assuming 'qt' is interpreted |
| 6 |
> as 'qt3' if only that is installed, rather than pulling in qt4 if not |
| 7 |
> already present). |
| 8 |
|
| 9 |
What? There will still be versioned dependencies in the ebuilds. |
| 10 |
|
| 11 |
> 2) What 'qt' means changes as new releases are made - if/when qt5 |
| 12 |
> becomes available, it means introducing a qt4 use flag and back-fitting |
| 13 |
> to existing ebuilds that used 'qt' but don't build against qt5. |
| 14 |
|
| 15 |
This is mostly untrue. The 'qt' flag means "build against the latest |
| 16 |
available qt that _this package supports_, not an absolute "build |
| 17 |
against qt5." Yes, you will need to introduce a qt4 flag as upstreams |
| 18 |
port packages to qt5, if they choose to also retain a qt4 frontend. |
| 19 |
|
| 20 |
Thanks, |
| 21 |
Donnie |
Archives