KDE 3.4 Coming in 3 Days
If all has gone well with the testing of KDE 3.4, we will see a final build on March 16, 2005. As far as I can tell, KDE 3.4 Release Candidate 1 is still masked by default in Gentoo — even for the ~x86 (experimental) users. So, I’m too lazy to unmask it and I haven’t tried it yet.
Check out the new features page and the release plan, marking the release for the 16th.
I hope they improved Konqueror. Right now, it doesn’t hold a candle to what Internet Explorer or Firefox can do.
For the moment, I’m emerging 62 updates. I have my nightly emerge on, but I have set my computer not to come on (it misses the cron job). I’m trying to get it all done so that I won’t be overwhelmed with the KDE release. Fun stuff.
March 14th, 2005 at 11:18 am
Well, what is hard with unmasking the kde?
(nah, the way that is approved by gentoo - adding all masked packages to packages.unmask sucks completely with projects such as KDE, where you have many subpackages).
you simply delete the input in packages.mask with some text editor and save it. Voila
Anyways. New KDE is great, period. Konq seems improved, and if all goes well I’m quite sure that Konq4 which is more and more based on stuff written for Safari will beat Firefox. Opera is out of reach for both, but K can beat Firefox on Linux for sure.
Being more accurate on the KDE - it is faster, looks better and runs smoother. Can hardly imagine what if the QT4 will be as good as they promise it to be. I think that many fans of the light WM’s will have another argument less at their side.
March 14th, 2005 at 1:53 pm
An easier way to unmask a package is simply to add the accept_keywords line before the emerge.
# ACCEPT_KEYWORDS=”~x86″ emerge kde
March 14th, 2005 at 2:28 pm
An easier way to unmask a package is simply to add the accept_keywords line before the emerge.
# ACCEPT_KEYWORDS=”~x86″ emerge kde
——-
I get what you’re saying. I’m saying that it is masked… even when using ~x86. I’m saying that I’m too lazy to use package.unmask. I use ~x86 by default.
I would not use x86, as packages are almost never updated to the point of having to update your system once every 6 months. Great for servers, but I don’t run one.
Personally, I think they should split it some more.
~~~~x86 — nothing is masked
~~~x86 — all release candidates and betas are unmasked, but leaving alphas masked
~~x86 — all release candidates are unmasked. Leave the betas and alphas masked.
~x86 — all finals are unmasked.
x86 — server stability. Finals that have been tested for months are unmasked. Everything else is masked.