27 Sep
2011
27 Sep
'11
1:41 a.m.
year my goal is also live for the moment
but with eapi=4
i am going to modify the kde4 eclasses to fit trinity
they have really nice functions to hande dependencies even circular depnedencies
by the way i have alredy made x11-libs/qt-mt-3.3.8c ebuilds with
libiodbc support (so no dev-db/qt-unixODBC)
but on the todo for the qt3 ebuilds is to change the install location
to /usr and name the qt3 incarnations of the programms ..-qt3 (cmake
findQT3.cmake also checks for these)
so no QTDIR hackery.
qt3 has been droped from portage so no need to stay compatible to the
old design.
it would be greate if trinity can be installed allong kde4 without
conflict s/kwin/twin/g
so everything to /usr
but thats another story.
2011/9/27 Fat-Zer <fatzer2(a)gmail.com>om>:
2011/9/27 Mario Fetka <mario.fetka(a)gmail.com>
Hallo Trinity Devs,
whats the state of tqt with qt4 ?
is it already possible to use qt4 with trinity or is qt3 still required
AFAIK - no. qt3 is still required... moreover: svn version requires a
special qt3 (locates in git)
i am asking because i am starting to package trinity for gentoo
and if qt4 works no need to stress with qt3 packaging
what kind of ebuilds are you going to write?
i'm currently writing live one's... here is an overlay:
https://github.com/Fat-Zer/trinity
It's not really finished now, but kdebase-meta builds ok.