| 1 |
Tomáš Chvátal posted on Fri, 09 Oct 2009 13:33:46 +0200 as excerpted: |
| 2 |
|
| 3 |
> Duncan wrote: |
| 4 |
>> What's up with kde-4.3.2? |
| 5 |
|
| 6 |
> Thats quite simple, 4.3.2 stay masked until we stable 4.3.1, stablebugs |
| 7 |
> are waiting on archies, we are hoping people will test for us. If we |
| 8 |
> unmask 4.3.2 everyone will migrate to it so we would be stabling |
| 9 |
> something not approved working. |
| 10 |
|
| 11 |
Thanks for the reply. It just felt quite weird seeing new 4.3.1-rX |
| 12 |
revisons coming out when 4.3.2 was widely announced, and I knew the |
| 13 |
ebuilds were available, because I caught them during the brief period |
| 14 |
when they were unmasked before the upstream kde announcement, and |
| 15 |
therefore weren't installable. But I knew why /that/ was so didn't |
| 16 |
mention it, just didn't know why they /still/ weren't unmasked. |
| 17 |
|
| 18 |
I was beginning to wonder if you'd decided to release 4.3.2 as 4.3.1-rX |
| 19 |
bumps, to save people having to upgrade the packages that hadn't |
| 20 |
changed... I guess that's more or less what the kernel packages do with |
| 21 |
the 2.6.x.Y versions, simply make them 2.6.x-rZ (Z has no direct relation |
| 22 |
to Y). But I never did gentoo kernels, preferring direct upstream (and |
| 23 |
am now directly on kernel git), so that never directly affected me. |
| 24 |
Using the same policy for kde4 certainly would have, tho I can't say I'd |
| 25 |
be entirely displeased with the idea. But it's probably a bit to early |
| 26 |
in the 4.x cycle for that yet. As it matures, there'll be less code |
| 27 |
churn in most packages, and it might be worth it. |
| 28 |
|
| 29 |
>> Meanwhile, what about kde-testing changelogs? |
| 30 |
|
| 31 |
> There will be no changelogs. Use git history. |
| 32 |
|
| 33 |
That's what I came to realize, sparked by thinking about it to write the |
| 34 |
question. So an hour or so after posting that, I had a scriptlet setup |
| 35 |
to do it for me. =:^) But if I'd have not asked the question, I'd |
| 36 |
probably have not thought of it, so asking the question was good, even if |
| 37 |
I did come up with my own answer. =:^) |
| 38 |
|
| 39 |
>> And if I do find a bug, do I check for and post it @ bugs.gentoo, or |
| 40 |
>> elsewhere? |
| 41 |
|
| 42 |
> bugs.gentoo.org is official bugzilla for official projects. So yes you |
| 43 |
> open bug in there. Just add prefix [kde-testing] to summary for easier |
| 44 |
> identification in the list. |
| 45 |
|
| 46 |
Thanks. It has been surprisingly smooth, here, every since you guys got |
| 47 |
the kde3 and kde4 stuff working well together! =:^) |
| 48 |
|
| 49 |
BTW, thanks! It was after that was working that I was finally able to |
| 50 |
get kde4 working to my satisfaction -- by tackling a single kde4 app at a |
| 51 |
time on a still mostly kde3 desktop. The problem was that at least at |
| 52 |
4.2.4, when I did the switch, the kde4 defaults both normal preferences |
| 53 |
and performance-wise were so incredibly bad, I couldn't get much of |
| 54 |
anywhere at all trying to tackle all of them at once! By tackling a |
| 55 |
single app at a time, getting it configured to my liking, then unmerging |
| 56 |
the kde3 version so the kde4 version would run when invoked, I was able |
| 57 |
to make the changes incrementally on an otherwise working desktop, and it |
| 58 |
worked *MUCH* better. The last two apps I tackled were kwin and plasma, |
| 59 |
the latter of which I did after finally switching to a kde4 desktop -- |
| 60 |
after configuring pretty much everything else. |
| 61 |
|
| 62 |
The point is, that was all possible because you guys had kde3 and kde4 |
| 63 |
working well side-by-side by then, so I could run kde4 apps on a kde3 |
| 64 |
desktop, without screwing up ksycoca or whatever. Had you guys not put |
| 65 |
in all that work to make it work, I'd have continued to have a /terrible/ |
| 66 |
time trying to get kde4 working, because it was just too much to try to |
| 67 |
tackle all at once. |
| 68 |
|
| 69 |
I don't know. That bit about running and configuring individual kde4 |
| 70 |
apps on a working kde3 desktop, may be worth adding as a hint to the kde4 |
| 71 |
upgrade guide... I know it sure helped me! |
| 72 |
|
| 73 |
Yeah, there are still bugs, but they're pretty much all upstream. You |
| 74 |
guys have done an amazing job with KDE here on Gentoo. Thanks again! |
| 75 |
And I know where (and how) to bug if I need to, now. |
| 76 |
|
| 77 |
>> Meanwhile, there's not a mailing list to follow what's going on more |
| 78 |
>> closely, is there? I obviously already follow this one. I suppose |
| 79 |
>> it's mostly IRC driven... and I'm not an IRC type of guy., |
| 80 |
|
| 81 |
> We are IRC driven guys mostly. :D So this is best tracker for you. If |
| 82 |
> you think this is too few informations, well bad luck, because we aint |
| 83 |
> going to improve it probably. If you want more infos on MLs then join |
| 84 |
> the irc and do the summaries. :P |
| 85 |
|
| 86 |
Who knows? Maybe someday. Meanwhile, running git whatchanged |
| 87 |
ORIG_HEAD.. regularly after syncing the overlay, looks like it should |
| 88 |
well cure that "running blind" feeling I was having. I'm happy it's git, |
| 89 |
as I'm not as comfortable with any of the other (D)VCSs. |
| 90 |
|
| 91 |
Thanks again! =:^) |
| 92 |
|
| 93 |
-- |
| 94 |
Duncan - List replies preferred. No HTML msgs. |
| 95 |
"Every nonfree program has a lord, a master -- |
| 96 |
and if you use the program, he is your master." Richard Stallman |
Archives