Are there any kde 4.3 packages for 13

vbatts · 10-23-2009, 09:52 AM

Quote:

Originally Posted by sahko

Yes its included. Its the source/kde/kdelibs/klocale.mutex.diff.gz file.
The three patches combined in one.

thanks to alienBOB for getting a hold of that patch and getting in the push 4.3.2 packages for -current.

slackd · 10-23-2009, 09:55 AM

Quote:

Originally Posted by Slax-Dude

Please read the very first phrase in my post

i know, i read your post. you'll some of the packages from current for kde to work properly. i kept that in mind when i replied.

Slax-Dude · 10-23-2009, 10:06 AM

Quote:

Originally Posted by slackd

you'll some of the packages from current for kde to work properly. i kept that in mind when i replied.

It is my understanding from reading this thread, although I could be wrong, that the KDE 4.3.1 packages would work on slackware 13.0 and that only KDE 4.3.2 would require an upgrade to slackware-current.
Is this correct?

MQMan · 10-23-2009, 10:30 AM

Quote:

Originally Posted by Slax-Dude

It is my understanding from reading this thread, although I could be wrong, that the KDE 4.3.1 packages would work on slackware 13.0 and that only KDE 4.3.2 would require an upgrade to slackware-current.
Is this correct?

That's my understanding to. I'm currently running 4.3.1 on a "stock" 13.0.

Cheers.

~sHyLoCk~ · 10-23-2009, 10:30 AM

Quote:

Originally Posted by Slax-Dude

It is my understanding from reading this thread, although I could be wrong, that the KDE 4.3.1 packages would work on slackware 13.0 and that only KDE 4.3.2 would require an upgrade to slackware-current.
Is this correct?

A few of -current packages as mentioned earlier in this thread are essential for making 4.3.1 work.

Slax-Dude · 10-23-2009, 10:33 AM

Quote:

Originally Posted by MQMan

That's my understanding to. I'm currently running 4.3.1 on a "stock" 13.0.

Quote:

Originally Posted by ~sHyLoCk~

A few of -current packages as mentioned earlier in this thread are essential for making 4.3.1 work.

So... which is it?

slackd · 10-23-2009, 10:36 AM

KDE 4.3.1 --> Works with Slackware Stable (Default)
KDE 4.3.2 --> Needs Current, as its compiled against them.

That's it.

~sHyLoCk~ · 10-23-2009, 10:39 AM

Quote:

Originally Posted by Slax-Dude

So... which is it?

Make it 4.3.2, typo.

I didn't notice you just want to use 4.3.1 packages and assumed you would want to upgrade to 4.3.2 instead, hence I suggested -current upgrade. My mistake.

Slax-Dude · 10-23-2009, 10:46 AM

Quote:

Originally Posted by slackd

KDE 4.3.1 --> Works with Slackware Stable (Default)
KDE 4.3.2 --> Needs Current, as its compiled against them.

That's it.

Cool! Glad that's cleared up

So... back to my original question: since I don't install "all" of KDE 4.2.4 in my slackware 13.0 machine, should I use

Code:

upgradepkg --install-new *.t?z

or

Code:

upgradepkg *.t?z

?[/QUOTE]

slackd · 10-23-2009, 10:54 AM

use this command as i said earlier:

Code:

upgradepkg --reinstall --install-new *t?z

Slax-Dude · 10-23-2009, 11:04 AM

Quote:

Originally Posted by slackd

use this command as i said earlier:

Code:

upgradepkg --reinstall --install-new *t?z

This will install packages that I don't have now in my working KDE 4.2.4
Any reason for this? Are there any packages needed by KDE 4.3.1 that were not needed in 4.2.4?

Sorry for nagging, but I'm not the "full install" type of user.
It makes no sense to me to install things I'll never use.

bgeddy · 10-23-2009, 11:14 AM

The scenario the posters are discussing may be safe at the moment but just to warn anyone browsing this thread - mixing Slackware -current packages with the stable release is not recommended and may cause serious problems. You have been warned

MQMan · 10-23-2009, 11:48 AM

Quote:

Originally Posted by Slax-Dude

This will install packages that I don't have now in my working KDE 4.2.4
Any reason for this? Are there any packages needed by KDE 4.3.1 that were not needed in 4.2.4?

Sorry for nagging, but I'm not the "full install" type of user.
It makes no sense to me to install things I'll never use.

Yes, there are some "new" packages, that didn't exist on 4.2.4.

It's easy enough to compare the list of what you have installed, what comes with 13.0, and what's in the new set. Then you can decide which of the "new" packages you want to install.

I ended up replacing what I had currently installed, plus ALL the "new" ones.

Cheers.

ryerke · 10-24-2009, 12:49 PM

I found that the 4.3.2 is enough of an improvement that it is worth the extra effort to install the necessary packages from -current. I am not (hereto-far) committed to staying with -current but I found that upgrading a few packages from the early part of the changelog and additionally the 4.3.2 packages from the announcement made for a significantly better system. Particularly KMail and Konqueror that were periodically crashing with 4.3.1. Aside from a few annoyances, 4.3.1 did run well on -stable.

enine · 10-24-2009, 02:44 PM

I downloaded everything from this tread http://www.linuxquestions.org/questi...urrent-763844/ and kde dies so I had to go back to the vbatts packages.