I don't think you'll need to build qt. It's available in the /extra directory:

ftp://ftp.slackware.com/pub/slackwar...a/kde3-compat/

For that matter, check out the other packages available in the /extra/kde3-compat directory. How much more is needed to build KDE 3.5?

Regards,

-Drew

If I understand correctly, the packages in /extra are for running 3.5.x apps within KDE4. That is, to provide a 3.5.x compatibility layer within 4.x.

The discussion here is about running 3.5.x without 4.x. Therefore, installing those packages is unnecessary and I'm guessing probably would cause problems.

Woodsman,

You may be right, but my impression is that the compatibility libraries are the libraries you'd need to run KDE 3. Just like one can install QT4 and run applications that require it in KDE 3.5 right now. It's not that one is installing some different version of QT4. In other words, the compatibility is provided by the required libraries themselves.

So, I'd think there's no need to build QT3 for Slackware 13, just use QT3 already provided in the kde3-compat/ directory (because it is QT3 build on Slackware 13). The same goes for the kdelibs3-3.5.10 package in the same directory. They are the things that you would build to run KDE 3.5.10 in Slackware 13.

So, after installing those two packages, what's left would be the non-library parts of KDE 3.5.10.

Regards,

-Drew

I agree that rebuilding probably is unnecessary. I'm only saying that installing qt3 from /extra is unnecessary for those already using 3.5.x. For example, those running 12.2. I think those packages are needed only for people running qt3 apps under qt4.

As I stated elsewhere, I updated 12.2 on my testing partitions to 13.0. I did not install the KDE4 or related packages, nor did I remove any of the KDE3 or qt related packages. I never installed any of the compatibility packages when testing 3.5.10 in 13.0. Everything worked.

If somebody is installing 13.0 from scratch but then wants to run 3.5 rather than 4.x, I think the person needs to be sure not to install the KDE4 and related packages. Then install all the KDE3 packages from 12.2.

Some people have talked about rebuilding all the KDE3 packages from within the new 13.0 environment. Somebody far more qualified than me will have to address whether that is necessary or prudent. :)

Ah, my mistake. I thought that's what you were discussing with General Failure. I missed your reply to him. :confused:

For what it's worth, I think it would be interesting to rebuild KDE 3.5.10 for Slackware 13 and provide the SlackBuild scripts, etc. This would be especially helpful for people who want to run Slackware 13-x64.

Just some thoughts,

-Drew

Sorry, wrong thread.

how do I use these patch files I tried to use them but it didn't work
where should the source files be where should the patch file be
and what should the patch options be
I've gone back to using bluewhite64 because KDE 4.2 is so bad

Are you guys still wanting to know if/how suspend & resume works on Slack-current? With or without the nVidia binary driver?

If so, I can say this: It worked fine for me on Slack 11 after I spent a couple days fiddling and wrote a script to do the suspend & resume for that. Certain modules cause problems, but I can't remember if nvidia was one of them on my system.

I need to check for my own usage, whether my script still works for Slack64-current anyhow, because XFCE doesn't suspend properly after the 1st suspend+resume, which is exactly what Slack11 did if I used the GUI suspend methods, which is why I wrote the script in the first place.

So anyhow, I'll post back about it in a while or tomorrow, once I verify either way.

Sasha

patch files.
 

Example using the Linux kernel:

Say you've got a kernel patch file called "filename" and you want to patch the kernel.

1) put the patch file into the root of the sourcecode.
2) enter that same directory.
3) type patch -p1 -i filename
4) that's it!

Sasha

Slack64-current suspend-to-ram works
 

Well, that was easy:

Suspend/resume to RAM works for me, just as fine as it did on Slack 11.

Currently: Slack64-current/kernel-2.6.30.5/XFCE/nvidia-185.18.31

And the nvidia driver, I'm not removing as it doesn't cause trouble. forcedeth however, I do remove, as well as ohci_hcd.

Updated script Here.

Also, as I have the time (though not necessarily the qualifications ;) ) if I can help out here, like for example taking a shot at patching Ark or something, just say so. If I think I can do it, I'll try.

Sasha