KDE-Forum.org

Well, I've tried building while not in KDE, in root, su...etc. I also tried one of the nightly builds (from 5/10). All of them have one thing in common: Either during make or install, they blow up when they try doing things with Ark. The one thing I want to fix!

I've tried newer builds too, and even trying to compile kdelibs blows up. I think I might as well give up for now and hope some other way comes to get around this thing without having to compile from source.

What a nightmare!

Sorry to hear that......................it's too bad SuSE hasn't gotten around to implementing that patch...........I noticed that Slackware uses that patch, so why not SuSE.....................That's why I suggest finding an upgraded SuSE rpm........................have you tried the update command for SuSE and see if there's something there??..........

Quoted

Original von thegeekster

have you tried the update command for SuSE and see if there's something there??..........

I think you mean the online package updater...SuSE calls it YaST2 and it's great...once SuSE gets around to updating stuff. KDE is still in 3.1.4 or something on YaST, and Kopete is on like 0.6 or something. Ridiculous! But I can't complain. Other than the ark thing (which is annoying but at least Konqy lets me get around it) I'm doing okay...

I did see Slackware had updated packages...I was tempted to try them since they, like SuSE, put kde in /opt/kde3. But apart from that I don't know what the similarities/differences are.

Ah well. I suppose I'll sit around and wait Thanks so much for your help!

Incidentally, I noticed that the diff file isn't really that big when I actually opened it. Does that indicate that the change is something minor that I could do to the already-installed Ark that I have? That may be an absolutely idiotic question but I figured I might as well ask...

Hmmmm.................the Slackpacks will put KDE in /opt/kde, but a creating a symlink called /opt/kde3 which points to /opt/kde is trivial..........

Slackware pkgs are nothing more than gzipped tarballs with a TGZ extension.................each pkg also has an "install" drectory which is where the package description is (called slack-desc) and an installation shell script called "doinst.sh", which sets up any symlinks needed by an application, and possibly some other configuration details..........

The main problem would be the backend configuration details...................in other words, how similar is SuSE to Slackware............enough to make it workable? The binaries themselves shouldn't be a problem, just the configuraiton...................One major difference is SuSE uses the System V style startup, while Slackware use the BSD style startup...............aside from that, you would have to know the inner workings of SuSE to figure out how to make it work.....................for a Slackware user, that shouldn't be much of a problem since he/she is used to dealing with configuration details................Not so with a SuSE user, since YaST does much of that for you................Some food for thought......

And the answer is No to your question about applying the patch after compiling.................a CPP file is a C++ source file for creating the binaries themselves..............the compiler transforms that ASCII source file into a machine readable binary format the computer can make use of.......... .....................Although, I wonder if replacing the compiled binary with an already patched one would work........

After a little thoguht, I wondered if there was a way to convert a Slackware pkg to the RPM format......................Slackware has a 'rpm2tgz' command, which converts RPMs to a TGZ file, so I thought why not the other way around

What I was able to find is the Alien package converter...............converting packages from one format to another......maybe it can work for you...

----------------------
Another one I found is slackrpm, which has a src rpm as well as a regular src tarball.......you can find it here

Quoted

Original von thegeekster

......Although, I wonder if replacing the compiled binary with an already patched one would work........

I'll have to give all these ideas a try. First and foremost though, it can't hurt to try to replace the Ark binary that I have with one (yours?) that is patched and known to work. Care to provide?

It's worth a shot, at the very least, and nothing that can't be very easily undone by saving my current binary. Hell, Ark is pretty much useless on my machine right now because of this, so I really have nothing to lose!

Your binary would be a huge help! Thanks again!

Just download the kdeutils-3.2.2-i486-1.tgz pkg from one of the Slackware mirrors.........You'll find it in the slackware-current/slackware/kde/ directory..............(A good, fast, current ftp mirror is "ftp.slackware.at")

Just be sure to rename any SuSE binaries you replace to something like: filename-suse in case something gets broken...........

However, you should be aware that it might not work as expected if SuSE passed different options when configuring the sources........if the binaries between the two packages are the same size, then it'll probably work okay.....................You'd be better off replacing the whole KDE installation for better compatibility, tho', to ensure the different KDE binaries will work together

-------------------------------
PS: To extract the pkg, just run the command tar -xzvf <package_name> in a temp directory........

Hehehe.........................after all this, I discovered where you can get SuSE RPMs for KDE-3.2.2.................................From a KDE ftp mirror....................look in the stable/3.2.2/SuSE/ix86/8.2 directory for SuSE 8.2 RPMs........Don't know if it uses the patched version of kdeutils.............

Yeah, those SuSE rpm's were the ones I used originally, but afiak they haven't been updated with the patch. I've looked back once in a while to see if they were updated, but it didn't look like it to me

I'll try the Ark binary from slackware. Worth a try! Otherwise, I suppose I could live with cmdline tar commands. The "extract here" service menu is awfully nice tho