After hours and hours and hours ... and hours (well, you know) of making every conceivable mistake, I finally got the script to create a working kde for me.
This is a long post in the hope that I can save someone the hours of aggravation. At least I can tell you a lot of what "not" to do, and list the packages I used as my sources.
Well, my present version is not entirely "working," but more like "proof of concept." I DO NOT have the actual kde desktop running -- there are some components missing, so it hangs up when trying to load.
I do have Kicker and Konqueror file manager working, which is something I was specifically seeking. I don't actually like the KDE desktop itself too much and prefer the speed of the JWM one. But, I guess I am one of two people on the planet who thinks Konqueror is the best filemanager around. (Even KDE is replacing it in 4.0 with Dolphin and relegating Konqueror to the shadows. So, of course, the other person who actually likes Konqueror would have to be the genius (IMHO) who designed it.)
The khtml component is not working, so Konqueror will not work as a web browser in my present install.
I imagine I can solve this by adding more packages, although I thought the "base" packages would work for this.
Warning ... once you tell Puppy to use kde by leaving the X-system to a prompt and typing "xwin startkde" forever after it will try to run kde. Which is a bad thing, if the kde desktop will not actually run. (After the crash and reboot, you may wish to type "xwin jwm" to get back to the default Puppy desktop.
The packages I used were from the slackware 12 repository located here:
http://www.slackware.com/packages/
My sfs file is 76 mb.
I used these packages:
acl-2.2.39_1-i486-2.tgz
arts-1.5.7-i486-1.tgz
k3b-1.0.2-486-1.tgz
kdelibs-3.5.7-i486-2.tgz
amarok-1.4.6-i486-1.tgz
attr-2.4.32_1-i486-2.tgz
kdebase-3.5.7-i486-2.tgz
libxcb-1.0-i486-2.tgz
I think the following are also necessary:
*Have the development sfs loaded.
*install the "qt-3.3.6 libraries for scribus, etc"
*install the libfam0.0.0 libraries (pup)
Now, being something of an expert on what NOT to do, here are some of my many mistakes:
*No matter how tempting, don't use your NTFS partition, even though it is mounting just fine and has lots of space. There are permissions problems (and also it compiles a lot slower on an NTFS drive).
*Do not re-run Mark's script with a defective version of the KDE sfs loaded. (Use the Boot configuration to unload it). The reason is that if you have some conflicting libraries in there, the new compilation may mistakenly use them.
*Don't take shortcuts. When unloading the KDE dotpup from a failed version, DO shutdown and reboot as it suggests.
On my PIII with 750 mb ram, it takes about 5 minutes to run the script start to finish. (I spent a lot of time waiting on the script when it was actually hung up because of permission issues on the NTFS partition). The clue of a hangup is that the icon in the start bar for the processor will show that the processor is working like crazy. (This does not happen in a normal run of the script.) Also, the value in the "ram remaining" block may disappear; and lastly, the desktop will become unresponsive and parts of it disappear when you click on stuff.
I had a lot of problems tracking down the dependencies. Part of this was due to my mistakes in setting up Puppy before starting the script process. So, I ended up compiling in GLIB-C and QT-3.3.8. This resulted in a running version -- but I also discovered Semonkey was broken.
Trying to fix that, I created a version that resulted in a pup_save file that causes kernel panic on boot. I managed to do that TWICE. (Fortunately, I use a "working" version of the save file, so rescuing myself wasn't too painful.)
Apparently what I was doing was mixing two versions of qt and glibc. In addition, I ran the script with out the development sfs loaded, but with the (defective) kde sfs loaded. As a result, I was getting very strange versions. For instance, I had qt and glibc compiled into the kde sfs, but kde was still claiming it couldn't find glibc. (And then Seamonkey was claiming it couldn't find it either.)
I don't yet know whether the development sfs is necessary to actually RUN the kde sfs (haven't tried removing it yet); and I'm also not certain about the qt-3.3.6. (I can't remember why I installed it or whether it was for this project. Initially, I was running the script on a Puppy version without the qt-3.3.6 installed -- a more stripped-down version, but after I crashed it I started using a version I had updated more.
Kicker will run, but so far, it's a bit weird about efforts to configure it. The first time I got it running, it came up behind the jwm startbar. The second time I got it running it came up on the left margin. Every time I have attempted to move it so far, it grays out the entire desktop (but continues to function.)
BTW, you will see "Amarok" in my list of packages because that is something I wish to get working. BUT IT DOESN'T WORK in this install. (I imagine I have to add in the kdemultimedia package and/or some other things). K3B doesn't work either, although as you can see, I installed that package.
I haven't yet determined whether I am simply missing kde packages, or whether there are further dependencies that I need to include. According to the KDE website, these packages should have been sufficient for a "basic" install.
Programs will launch from Konqueror and Kicker. It's not clear to me with OpenOffice whether it is opening in a KDE window frame or a Gnome window frame. (I originally installed OpenOffice direct from OpenOffice.org and it was opening without any frame at all. I modified the soffice script to add the gnome windows, following a hint I found somewhere on this forum.)