1 |
Quite the hassle. I would suggest maybe you try Trinity Desktop as a |
2 |
replacement. I haven't tried it in a while but it generally was ok at a |
3 |
functional KDE3 desktop that is compatible with modern system-related |
4 |
libraries. They usually ported a larger number of old KDE 3 apps on |
5 |
request, though I'm not sure how it stands right now. |
6 |
|
7 |
For lovers of the old code base, there was a guy who added patches for |
8 |
udiks and upower to the old code and fixed GCC compile bugs, though I have |
9 |
stopped following new developments a good while back. My understanding is |
10 |
that if you mostly only wanted old stuff, it was your best option and it |
11 |
was being built for OpenSUSE distros for people that wanted to try it out |
12 |
without going all the way to TDE packages. |
13 |
|
14 |
Tiago |
15 |
|
16 |
On Sat, Jul 4, 2015 at 1:20 AM, Brent Busby <brent@×××××××××.org> wrote: |
17 |
|
18 |
> Tiago Marques <tiagomnm@×××××.com> writes: |
19 |
> |
20 |
> > Besides that, were you actually able to use the desktop? A good while |
21 |
> > back I was having issues with newer GCCs, HAL, consolekit and other |
22 |
> > parts of the desktop's subsystem. |
23 |
> > |
24 |
> > My experience is ABI_X86 has unfortunately introduced conflicts |
25 |
> > everywhere, not just on this overlay. |
26 |
> |
27 |
> Up until now, I've been able to find ways around everything. There was |
28 |
> always some patch to get around most (but not all) GCC issues. I got |
29 |
> around HAL by not using it, and using the KDE 4 version of programs like |
30 |
> K3B that cared about HAL. I got around consolekit by just making my |
31 |
> launch of KDE include 'exec ck-launch-session dbus-launch --sh-syntax |
32 |
> --exit-with-session startkde', which registers the session. (Later I |
33 |
> just globally got rid of consolekit, since it's pretty annoying even |
34 |
> outside of KDE, as is policykit, and all those kits.) |
35 |
> |
36 |
> But I've got no solution for this. It doesn't appear to be all |
37 |
> multilib's fault though. It looks like all packages that used to be |
38 |
> under kde-base/ in main Portage are now under kde-apps/, and this |
39 |
> expectation has carried across into the overlay somehow. Since the |
40 |
> overlay is not updated for this, it's causing most of KDE 3 to appear to |
41 |
> be missing to Portage...or at least that's how it looks so far. |
42 |
> |
43 |
> I may just give it up. I mostly wanted KDE 3 to continue for two |
44 |
> things, now no longer necessary for me: |
45 |
> |
46 |
> - I had it configured to look like CDE. Yes I know lots of people think |
47 |
> CDE is ugly, but I like it, and KDE 4 is incapable of getting that |
48 |
> look quite to the degree KDE 3 could. It doesn't matter so much now |
49 |
> that real OpenGroup CDE has been open-sourced and is being vigorously |
50 |
> supported by community people who care about it. You can now make |
51 |
> your Linux workstation look like HP-UX til the end of time if you |
52 |
> want. |
53 |
> |
54 |
> - I liked the HTML editor Quanta, which is a QT3 only program. Lately |
55 |
> though, I've been becoming more and more of an Emacs person. (It's |
56 |
> got me. GNU Emacs happens to people when they least expect it.) As |
57 |
> part of that growing disease, I've become attached to Emacs' various |
58 |
> modes and assistants for HTML, CSS, Javascript, etc., so I don't |
59 |
> really need Quanta so much anymore either. |
60 |
> |
61 |
> Oh well...farewell KDE 3. |
62 |
> |
63 |
> -- |
64 |
> + Brent A. Busby + "We've all heard that a million monkeys |
65 |
> + Sr. UNIX Systems Admin + banging on a million typewriters will |
66 |
> + University of Chicago + eventually reproduce the entire works of |
67 |
> + James Franck Institute + Shakespeare. Now, thanks to the Internet, |
68 |
> + Materials Research Ctr + we know this is not true." -Robert Wilensky |
69 |
> |
70 |
> |