Gentoo Archives: gentoo-amd64

From: Duncan <1i5t5.duncan@×××.net>
To: gentoo-amd64@l.g.o
Subject: [gentoo-amd64] Re: Updates other than the masked one
Date: Wed, 30 Dec 2009 23:24:07
Message-Id: pan.2009.12.30.23.22.34@cox.net
In Reply to: Re: [gentoo-amd64] Re: Updates other than the masked one by Martin Herrman
1 Martin Herrman posted on Wed, 30 Dec 2009 21:51:23 +0100 as excerpted:
2
3 > actually, I had already read [the bug] before I wrote the original
4 > posting. I just didn't realise that I could 'safely' unmask the package
5 > (because I already had chosen to run the unstable KDE4.3 release).
6
7 Good, you put the "'safely'" in quotation marks. Given that you already
8 chose to run the unstable kde4.3, it's no /additional/ risk, and actually
9 is by far less trouble than otherwise, but you obviously realize the
10 (measured) level of risk you take going with unstable kde4.3 or you'd
11 have not had to use those quotation marks around /safely/.
12
13 =:^/
14
15 > I like the concept of Gentoo, the power it gives to me, the safe
16 > bleeding-edge apps and the ease in which I can run my own custom build
17 > kernel. But on the other hand: I just need a working desktop and in 98%
18 > of the cases I don't want to dive into all the details to get things
19 > working. This seems to be a contradiction, I should have been an Ubuntu
20 > user, but that's not true :-D Now and then I apply some custom
21 > USE-flags, but I stick to the default install as much as I can so I'm
22 > not the one to discover bugs.
23
24 ... but you didn't quote "safe" there. =:^\ Maybe that's because it's a
25 bother when you already quoted it above, but anyway...
26
27
28 Really, truth be known, from my perspective the whole kde thing is
29 screwed up right now -- and not by Gentoo, but upstream kde.
30 Unfortunately there's a kde conundrum. kde4 is still under /very/ heavy
31 development, and still has significant enough bugs that to call it
32 "stable" in /any/ form remains a bit of a stretch. Honestly, despite kde-
33 upstream's claims about kde4.2, even kde4.3 is only now reaching late
34 beta, 4.2 was early beta or late alpha, 4.1 was early alpha, and 4.0 was
35 only a conference level technology preview. By many predictions
36 (including but not limited to my own), 4.4 should finally be release
37 candidate level, no real show-stoppers but still somewhat rough around
38 the edges. Following that trend, 4.5 should finally be more or less
39 ready for normal/ordinary use -- full release. (Well, there's a possible
40 exception for kmail, which will be switching to akonadi with 4.5, but
41 they are said and one hopes it's true, to be taking their time and
42 getting it right, the reason they didn't try for 4.4. Perhaps that's the
43 "less" of "more or less", above.)
44
45 Given that, in a sane world, kde 3 would remain supported and with us for
46 another year, thru 2010 at least, since 4.4 is scheduled for February,
47 4.5 for August, and there should be at least a few months of overlap to
48 give people time to sanely make the change before the end of support for
49 the previous stable version.
50
51 Unfortunately, by that metric, kde no longer belongs to a sane world
52 (which of course implies serious questions about the sanity of those who
53 still use it... like me and obviously you, but be that as it may...),
54 since it dropped kde3 support with the release of 3.5.10 and 4.2.0. And
55 of course the qt3 upon which kde3 is built was EOLed before that (tho
56 I've never checked the specific timing on that end, only taken kde's word
57 for it).
58
59 Unfortunately, but those are the facts on the ground as distributions and
60 ultimately us users must deal with them. Simplest terms, that leaves us
61 users stuck between a rock and a hard place. We have three choices:
62
63 (1) Dump kde entirely for something "sane".
64
65 While this might be the "sane" choice, many users don't find it
66 particularly viable, for whatever reason.
67
68 (2) Follow kde3/qt3 off into the sunset, at least until kde4 is found
69 suitably stable (for various definitions of "stable"). That's likely
70 another year if we're lucky for traditional "stable" distribution users,
71 including gentoo stable arch users. For those like me who enjoy testing
72 betas, the current 4.3 is about right. (I switched with 4.2.4, but it
73 was **EXTREMELY** difficult, over a hundred hours of /extra/ work,
74 hacking scripts to replace broken functionality, etc, in /addition/ to
75 the usual and expected upgrade hassles. Few have the time even if they
76 had the motivation and skills for such an undertaking.). Obviously, the
77 real bleeding edge folks, or those who are generally content with the
78 default/common functionality, could have (and many did) changed earlier,
79 while those between the beta/unstable tester folks like me and the stable
80 folks, will find a point in the middle to switch.
81
82 (3) Undertake a "forced" upgrade to kde4, likely before one would have
83 otherwise done so.
84
85 Actually, I did this, as I had been /trying/ (and failing) to do the 4.x
86 upgrade since before 4.0, and would have definitely waited until at least
87 4.3, had kde3 not already been marching off into the sunset. (I like to
88 give myself plenty of time, and get the conversion done well before the
89 drop-dead date, which I did, tho at enormous cost in time and hassle.)
90
91 Meanwhile, and this is the point of the message, for those choosing #3,
92 because kde4 /is/ under such intense continued development, and because
93 it /does/ have such serious bugs remaining, once one is on kde4, the
94 latest stable upstream kde4, thus for Gentoo users, ~arch keyworded kde4,
95 since it takes some time to stabilize on Gentoo, is likely going to be
96 less trouble than stable kde4, because more bugs are fixed upstream, and
97 the major kde4 integration issues are already dealt with at the
98 gentoo/kde level, so what remains is rather minor integration bugs for
99 ~arch, as the measured risk for getting the DEFINITELY more bugfixed
100 latest from kde upstream.
101
102 Given all that and being the beta tester type I am, I'd probably actually
103 be running the kde-4.3.8x kde-4.4 betas from the kde overlay, except that
104 I have another major project I'm working on ATM -- getting my Acer Aspire
105 One netbook up and running on Gentoo. But that's close, and I may or may
106 not get to the 4.4-rcs before the 4.4.0 general release.
107
108 (FWIW on the AA1, I have the completed image done on my main machine,
109 copied to USB stick, copied from there to the AA1's drive, and tested
110 booting. But I screwed up the grub install somehow and thus still have
111 to boot from the grub on the USB stick, but to the installation on the
112 hard drive, so I have that to figure out still, and then I still have X
113 and kde to configure/customize, networking to get running, etc. A few
114 hours more work, probably, but it's /almost/ there! I'm hoping to have
115 it running tomorrow, before the new year starts, at LEAST the grub bit
116 worked out, and hopefully xorg, with the syntouch config for the evdev
117 driver and the extra keys. If I'm still running the default kde4.3 as
118 the new year comes in, but have the grub issue traced and resolved, and
119 xorg/keyboard-extra-keys/syntouch configured, I'll be happy. =:^)
120
121 (But what I'm /really/ looking forward to for the netbook is the
122 plasma-netbook aka plasma-newspaper layout, tho that's kde4.5 material
123 I think.)
124
125 --
126 Duncan - List replies preferred. No HTML msgs.
127 "Every nonfree program has a lord, a master --
128 and if you use the program, he is your master." Richard Stallman