On Fri, 20 Jul 2012 03:07:38 -0400
Philip Webb <purslow@...> wrote:

> For most activities, I use Fluxbox on Gentoo with a number of KDE 4 apps.
> However, there are  2  KDE 3 apps which I really value
> & which have not been ported -- or not adequately -- to KDE 4 ,
> ie Kmahjongg & Kworldclock; I would also like to keep Ksokoban around.
> 
> Currently, I have them installed with supporting libs in an overlay :
> 
>   O/LAYS -- kde-sunset : rebuilt for libpng15
> 
>     111107 kde-base/kdeartwork-kworldclock-3.5.10
>     111107 kde-base/kdelibs-3.5.10-r6 [ ~ : 13 min ]
>     111107 kde-base/kmahjongg-3.5.10
>     111107 kde-base/ksokoban-3.5.10
>     111107 kde-base/kworldclock-3.5.10-r1 [~]
>     111107 kde-base/libkdegames-3.5.10 [for kmahjongg etc]
>     120630 net-dns/libidn-1.25 [for kdelibs3]
>     111107 x11-libs/qt-meta-3.3.8b-r2 [for KDE3]
> 
> That's from my homemade list of installed pkgs.
> 
> KDE 3 is no longer supported by Gentoo & will probably become unusable
> in the near future after some further update of the pkg-manager Portage.

You mean because of the way it's been complaining about the location
of the EAPI line in the kde-sunset ebuilds lately?  That's a simple fix, I
think:  someone just has to find the time to swap the order of the
KMNAME and EAPI lines, and the complaints should go away.  For
such a small set of packages, you can probably do it in a local overlay
until kde-sunset catches up.

> Therefore, I would like to install the Trinity versions of the above
> -- 'qt-meta:3' is a regular Gentoo pkg & sb ok as it stands --
> & the correct place for them seems to be  /usr/local .
> I don't want to install the rest of Trinity, which I wouldn't use.
> 
> Is this feasible & does anyone have basic advice how to go about it ?
> I have 'git' installed, but am not a developer & have never used it as such:
> it merely provides background support for the 'sunset' overlay.

Unfortunately, There Is A Problem with creating ebuilds for the Trinity
packages that still use autotools to build, among them kdetoys and kdegames.
kworldclock was one of the applications that I was specifically *not*
able to make work.  We need someone knowledgeable about autotools and
the kde-sunset eclasses to help unravel the knot, and so far no one has
volunteered.

You can try building the packages by hand without Portage's intervention
(if you do, please drop a message to the list to tell us how it goes);
otherwise, you may be stuck waiting for the low-priority packages to
be ported to CMake along with the rest of us.  Note that the version of
QT3 that ships with Trinity is slightly different from 3.3.8b, so you
may need to replace that, too, if you go the manual route.

Sorry I can't give you better news.