|
If memory serves me I updated KDE via cervisia which can be ran via the "run" dialog box or via the menu. It is the cvs repos manager for KDE.
I am not a KDE user (it was the first X-class desktop I used on FreeBSD but it got too "busy" for my likings) KDE is installed only on this box as it is a full Slack install of everything on the Slack disk package (then I removed what I would not use) KDE did remain and I have ran it 2 or 3 times via a custom made "startk" and "kinitrc" (startx and xinitrc modified). I also run certain KDE utilities from within dropline-gnome (yes you can and on a FreeBSD box gnome has a kde menu for kde) During the first run of KDE I did the update. During the swaret is when I noticed that KDE included "i686" packages and having broke a dropline-gnome previously with i486 packages I EXCLUDEd KDE.
There are lots of threads about swaret breaking things I (knock on plastic, wood not available) have had no problems with swaret upgrades. The threads refered to mostly x-enviroments, desktops and sound. That should point someone NOT to upgrade gnome, dropline-gnome (has own utility), kde and alsa via swaret.
Downloading packages and hand installs are not hard and can at times be more inline with your computer/OS enviroment than a "vanilla-one-size-fits-all" package. There are ppl who will say "it is not an 'offical' slack package" or "it is not built for slack" neither of which is entirely true since a platform-independent package when built in your enviroment becomes built for slack and your computer specifically. That is pretty "offical" to me. That is also one reason for the ./configure for these builds, to configure the make to your system. About the only requirement is to have ALL the development sources and tools installed as well as your currently running kernel sources properly configured.
On the i486 vs. i686 packages. I am not refering to setting an option during a build. The i486 packages as you mentioned above in tuneing builds will work on processors classes going back to the first pentium class to the latest p4ht processors. However i686 class packages that are released in "boxed" set .tars packages of available programs have been rewritten for optimisation to i686 class processors (P2 and greater) and do not work below that. Also these builds work together as a "set" if you overwrite a i686 package with a i486 package (example being dropline-gnome) you will break the install of the "set" (experience proven). There is also info about this at droplinegnome.org.
|
