right ok I am proberbly being a numpty here, no I didn't realise that KDE 4.2 doesn't allow icons on the canvas, I have learnt something there, it's the no menu button that confuses me.

I just used Swaret to upgrade to 4.2 without even running KDE 3.5 after a clean install so I will let you know what happens then.

You mention a recompile, sorry I am a new to hardcore slackware so I am not sure what you mean with regards to this, I understand compile it's the source slackbuild bit I don't.

slackbuilds.org

Otherwise known as SBO.

It's a collection of source code packages for slack with a standard compile and installation method.

Use it, love it.

Ginger,

you have already been told twice that there are no available packages for KDE 4.2 compatible with Slackware 12.2.

Swaret won't help you on that. By the way it is not part of Slackware and you use it at your own risks.

If you need 4.2, either use Slackware-current -- knowing that it is not intended for production -- or use a Linux distribution which ships KDE 4.2.

A specific version of a distribution is a (willingly) consistent set of software, you can try to add a part not intended for it but do not complain if it does not work.

Didier Spaier, If you read the above I downloaded 4.2 from Slackware-current.

Ok maybe Swaret isn't the best tool to use, can anyone recommend one or give me a pointer to a HOW-TO document for the KDE upgrade.

Just so everyone understands "I downloaded 4.2 from Slackware-current"

Yes but you are using -current packages on a 12.2 system.

Many of the packages and libraries are no longer compatible between the two.

Either upgrade to current or rebuild the packages for 12.2.

Ah ok, I thought that as I had installed a vanilla Slackware 12.2 from the DVD and then tried to upgrade to the current that would be good enough. I did upgrade all the packages from current not just the KDE packages.

Ok well if you followed the instructions in the readme's you should be fine.

I'd recommend slackpkg to do such and upgrade

try

If you did upgrade everything to -current that should be fine -- provided that you upgraded glibc-solibs before any other package, as stated in the CURRENT.WARNING file.

To update you system, use the Slackware tools: pkgtool, installpkg, removepkg, upgradepkg, or even better slackpkg. All these tools are well documented, see man <toolname>.

For instance to upgrade from Slackware 12.2 to Slackware current you could have done this - I suppose that you have slackpkg installed, which is the case if you made a full install:
1) Edit the file /etc/mirrors to un comment one of the mirrors' URL and modify it so that it ends in -current
2) Read /etc/slackpkg/slackpkg.conf then edit it as you see fit
3) run "slackpkg update"
4) run "slackpkg update gpg"
5) run "slackpkg upgrade glibc-solibs"
6) run "slackpkg upgrade-all"
7) run "slackpkg install-new"

You can run "slackpkg new-config" also to check for new configuration files and will have to remove packages that were included in -12.2 but are not included in -current.

Whatever the tools you use, reading the Changelog for -current to check what has to be done in the process of upgrading is a must.

Obviously if you upgrade a kernel you have to run lilo again.

If you ever need a package not included in Slackware you can very often get a so-called SlackBuild for it @ http://slackbuilds and use it to make yourself and install a package. Be warned though that they provide SlackBuilds for stable releases, not for -current.

For your information I do run Slackware-current in a virtual machine. I do not have icons in KDE 4.2.1 -- I don't care as I do not use icons anyway -- but I have window bars at the top of windows.

Note. Edited post for sake of completion after having read other responses.

so after reading this I I loaded 12.2 on a desk top then switched my repository mirror to http://slackware.cs.utah.edu/pub/sla...kware-current/ it is fast
then did from run level three I did a slackpkg update then did a slackpkg upgrade-all
then I did a slackpkg install-new. Note I used all new configuration files then to see my old icons I right clicked the the desk top left clicked appearance settings and then chose folder view. you will find some of your icon picture do not have pictures any more do to pixmaps changes. after a while you will learn that you do not need the icons in kde4.

The instructions I gave were directed at ginger since he seemed to have completed the first steps of the install already.

When starting from scratch the advice that Didier gave should be followed but with the addition of an "install-new"

yes I see this so I installed it like ginger did and also went back and did a fresh to see if we had a problem with the mirror or something. this thread is. KDE 3.5 -> 4.2 Current sorry to confuse anyone i was just trouble shooting it for my favorite Distro. you will also see the new version is 4.2.1 and the testing was 4.2. anyway if you use a current mirror it will upgrade to 4.2.1 no trouble here.

Right Guys,

I followed this to the letter using ftp.mirrorservice.org.uk

1) Edit the file /etc/mirrors to un comment one of the mirrors' URL and modify it so that it ends in -current
2) Read /etc/slackpkg/slackpkg.conf then edit it as you see fit
2) run "slackpkg update"
3) run "slackpkg upgrade glibc-solibs"
4) run "slackpkg upgrade-all"
5) run "slackpkg install-new"

On option 3 I said to over write the files, I then tried to carry on with option 4 only to get lots of warnings and gpg error.

As I said I am quite new to this but it's starting to give me the hump.

Ginger

I am a bit surprised as I do not see ftp.mirrorservice.org.uk in /etc/slackpkg/mirrors.

Anyhow if you have gpg errors this could be a problem with the mirror. You could try this URL:

ftp://slackware.mirrors.tds.net/pub/...kware-current/

It is usually fast and reliable.

If you do so, do not forget to issue 'slackpkg update' again.

As a side not, I must admit I didn't upgrade from -12.2 to -current. In fact I made a local mirror of -current using rsync, then made an ISO image of the tree and booted it in a virtual machine.

sorry I ment http://www.mirrorservice.org/ I must be getting old as my memory is failing me :)

Just out of interest which is the best option to take when I have upgraded the GLIBC-Sollib Keep, Overwrite, sorry cannot remember the other too :)

No problem for the wrong URL, I find myself mistyping in almost every post ;)

If I remember well the other options are Diff and Prompt.

To give you an advice about the option to take, we need to know which file would be updated.

Anyhow I would either choose Keep and later on issue 'slackpkg new-config' to be asked again what to do with the .new files, or Diff to check the differences between the old and the new file then decide either Keep or Overwrite.

If you choose replaying the upgrade from start using a new mirror, double check that one and only one URL be un commented in /etc/slackpkg/mirrors