Damn it all! KDE 4.4 even makes me want to try it out! even after my beliefs that Fluxbox is all people need.

Thanks in advance Erick. I'll wait the weekend to download and play with it for the whole 'carnaval'.
Let 13.1 cook the time it needs =]

The XFCE developers pushed back the 4.8 release date to June 12th from April 12th as they first had announced so XFCE is gonna be a while http://foo-projects.org/pipermail/xf...ry/026609.html

On the other hand, since libnotify has been added to Slackware now it would be useful to rebuild exo with it present.

Great! Thank's Eric.

I already downloaded, put on slackware current and burned. Tonight I will test and post the results here!

[]'s

Installed without a hitch. Thanks mate!

Hello,
Can someone tell me when will be KDE 4.4 moved to current?
Or are there some plans to keep KDE 4.3.4 in current?

Thank you for any information.

Best regards,
Jack.

Cheers

KDE 4.4.0 will not be added to slackware-current. That is the reason why I am building these packages and making them available "unofficially". The reason being that KDE 4.4.0 has requirements which Slackware can not satisfy. As a result, the KDE 4.4.0 Slackware packages (the ones I built) miss certain features that require authorization through PolKit: for instance there is no font installer, and it is impossible to change the computer's time and date in KDE 4.4.0. Perhaps other stuff is missing too which I have not yet found, because during compilation I saw many hints that stated "if you would have had polkit you would get extra functionality".

KDE 4.3.5 will get added to slackware-current soon.

Eric

Thank you very much Eric!
Will Slackware-current become satisfy the
requirements KDE 4.4.0 has? Sometime? I would
like this very much. ;)

Best regards,
Jack.

Cheers

Ps: Sorry for my bad english.

Personally, I view that as a good thing. :)

Notice that after the kde 4.4 install in both my -current and 64 -current/multi that slackpkg upgrade-all wants to bring back the 4.3 version. Normal behavior I assume given that 4.4 is not "official"?

Of course. This happens because slackpkg wants to make your system match the official Slackware package set for the version you configured.

Eric

Speaking of slackpkg, you wouldn't happen to have a convenient list of packages to blacklist so that it doesn't wipe out KDE 4.4, would you?

Has anyone told you lately, Alien Bob, how much you are appreciated?

This thread might prove helpful.

http://www.linuxquestions.org/questi...ight=blacklist

A list of all packages you have installed which carry my "alien" tag (like the set of KDE 4.4.0 related packages) can be obtained by running:
Dump the output of that command into /etc/slackpkg/blacklist.

You may want to consider if you really want to blacklist the "dependencies" (i.e. the non-KDE core packages) this way, because I know for a fact that ibv4l is going to enter slackware-current soon, and strigi as well as libxklavier packages are going to be upgraded at the same time.
Perhaps you want to use the official packages once they enter slackware-current.

Eric

But, according to your previous post, they won't...?

gargamel