Reading through Eric's README and Slackbuilds it appears that the simply running the Slackbuilds for DEPS and then KDE itself and then removing the packages specified in the README will result in a fully installed KDE 4.7.2. I just wanted to run this by a few others before I made on obvious error?

It should just work
I've used these scripts to build 4.7 and did not run into any problems.

I like the simplicity of it. Appears to be modeled after the X11 modular build scripts. Makes it easy to add/remove your own packages, options, and patches.

Well I'm playing with KDE 4.7.2 on 13.37 (not current) with the packages from /patches installed and the updated mesa from testing per Eric's instructions. The SlackBuilds do in fact build and install to a working KDE, which I thought I remembered from a previous KDE build with Eric's scripts.

I had some trouble building, but I'm not sure it had anything to do with the SlackBuilds or not running current. I couldn't get the kdeplasma-addons to build, until I first removed the packages that Eric says to remove after installing the new kde-4.7.2 packages if you go that route. The SlackBuilds for KDE and the DEPS are so nice, it's really a non-event. It just takes time to run.

I will be playing with it for a minute to see if everything is stable. It's a really nice look, so I hope it works out!

My instructions are for installing my packages, not for building them from source. If you want to build from source, be my guest (they are easy to compule using the SlackBuild scripts I wrote) but that is not what I am supporting. My "ktown" repository is a package repository, and the SlackBuild scripts are basically just a reference. The packages that I built work well, and I know how I built them.
If you have issues with packages that you built yourself, then you have to find the solution yourself.

Eric

Lol, yes I knew I was deviating from the instructions just by using 13.37 instead of -current, which is really why I wanted to build them myself vs. installing the packages you had built for -current, plus it's just more fun to do it this way! I read your cautions and considered them carefully, which was why I asked here, to see if anyone had gone down this road previously. The build scripts are VERY nice and everything was documented well, so that on the one hang up I had, the answer was easily deciphered. Your README indicates that you would give no guarantees for 4.7.2 on 13.37 which is yet another reason that I chose to share my experience just in case others were curious as well. No complaints whatsoever on my part here.

As always thank you for all of the great work, packages, Slackbuilds, etc!

For the record, I have emails and blog replies from several people who confirm that the KDE 4.7.2 packages work fine on Slackware 13.37.
With the speed slackware-current is evolving, it will be safe to say that even 4.7.3 packages will still be usable on Slackware 13.37 when those are released next week (with a bit of luck I can start compiling before the weekend).

Eric

1 members found this post helpful.

i used the same packages, after a fresh install of slack-current. everything worked fine and it was quite stable to, untill this morning.

yesterday night, before i go to bed i was trying to run aptana studio 2. i had to install xulrunner and jdk packages (13.37) as required. so i installed them. i was shuting down the computer then i saw the messages saying "akonadi server shut down. too many chrashes" many times on the screen. i didnot pay much attention then but this morning i started the machine and it booted xfce. i restared it as root and choose kde on xwmconfig and started x and it loaded xfce again.

so i just format the machine and keep going from 13.37 with xfce now.

well, for one week i had a nice kde experience and i thing kde is getting better compairing with the others.

I am really please with KDE 4.7.2 and 13.37 in general. I have done no tinkering with samba or anything else since setting up this machine , and I was working on my win7 laptop and came back to this machine and saw an alert from the device alerter that my windows machine had automatically been detected! That's something really new and interesting to me. It seems a lot of interesting new features that I was totally unaware of are there to be investigated!

Also rekonq now seems to be a very usable browser. I still can't stand dolphin compared to konqueror, but I think rekonq may just win out over chrome if it keeps going on this way!