Summary: | Opera 7.23 ebuild has wrong QT version dependancy | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Niek van der Maas <webmaster> |
Component: | New packages | Assignee: | Heinrich Wendel (RETIRED) <lanius> |
Status: | RESOLVED WONTFIX | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Niek van der Maas
2004-02-28 05:39:36 UTC
sorry, since kde-cvs ebuild is not offically supported and opera most likely won't work with qt 4, i can't change that I do _NOT_ agree with this. It will take at least 6 months from now before Qt 4 will go beta. It's really stupid to force users _NOW_ to install the stable Qt ebuild when they've also installed Qt 3 from CVS. At the time Qt 4 is out we can simply modify the ebuild to fetch another tarball if availible (knowing Espend Sand, this will be the case) or just block Qt 4 users. The package net-p2p/azureus-bin (and I guess more packages) has exactly the same problem. It depends on =x11-libs/qt-3* and =kde-base/kdelibs-3*. This is even more stupid: the systraydaemon part in Azureus is compiled from source, and because Qt 4 will be 99% source compatible with Qt 3 forcing users to install Qt/KDE 3 is plain wrong. You should have this problem with every ebuild that uses the kde elcass since "need-qt 3" adds the following dep ~x11-libs/qt-3. We don't support the cvs version of qt so we won't change the dep, you can change the naming scheme of your ebuild to 3.YYYY.MM.DD. |