On Saturday 02 July 2005 22:54, Caleb Tennis wrote:
> While your proposal works okay for the qt4 scenario, I'm more concerned > with the existing qt3 at the moment. As is, I stil l don't see a way > around what has been proposed for those ebuilds. Until portage has the > ability to handle && deps, I fear there's no real way around it. I don't > think we'll have time to wait much longer; I expect ebuilds that need qt4 > will start appearing in portage soon and the minute that qt4 is marked > ~arch it instantly creates the dependency mess addressed previously. We can start porting those ebuilds that just need to be changed using "=x11-libs/qt-3*". Then we can change kde-functions.eclass for the ebuilds using need-qt() (which can set something like e.g. || ( =x11-libs/qt-3.3* ... =x11-libs/qt-3.1* ) ); and finally we can deal with the remaining ebuilds (not many probably) using the qt.eclass (or qt3.eclass, or qt3-info.eclass, or whatever), or again something like "|| ( =x11-libs/qt-3.3* ... =x11-libs/qt-3.1* ) )" where possible. -- gentoo-dev@gentoo.org mailing list
