LinuxQuestions.org
Download your favorite Linux distribution at LQ ISO.
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 03-02-2004, 09:32 AM   #1
ferreter
Member
 
Registered: Oct 2002
Location: USA, IL
Distribution: Debian/Gentoo/Slack
Posts: 215

Rep: Reputation: 30
kde 3.2 -> is it worth upgrading?


Hey all,

Got Slack w/ KDE 3.1 running now and I was wondering if there is an easy way to update it to 3.2. Is it even worth the upgrade anyways?


Thanks!
 
Old 03-02-2004, 09:44 AM   #2
guygriffiths
Member
 
Registered: Jun 2003
Location: Reading, UK
Distribution: Debian 3.0, LFS
Posts: 524

Rep: Reputation: 37
Not sure how to easily upgrade to KDE 3.2 in Slackware, but I imagine it's pretty simple.
However, IMO it's not really worth it unless there is something specific that you want.
Pros:
a) Nicer eye-candy
b) Slightly faster loading time
c) If you use Konqueror as a web browser, it has been greatly improved (or so I'm told - I use Moz)
Cons:
a) Programs crash slightly more often
b) The hassle of installing it all

Having upgraded, there was nothing that made me want to go back to 3.1.4 (which would have been as simple as changing a symlink), but the improvements, whilst there, are not particularly obvious in the way I use it.
 
Old 03-02-2004, 09:50 AM   #3
KMcD
Member
 
Registered: Jun 2003
Location: Dublin, Ireland
Distribution: Slack -- current
Posts: 354

Rep: Reputation: 30
use swaret, very easy to upgrade to kde3.2. Just be careful that it checks for dependancies. Also better upgrade alsa & arts too.
 
Old 03-02-2004, 09:58 AM   #4
guygriffiths
Member
 
Registered: Jun 2003
Location: Reading, UK
Distribution: Debian 3.0, LFS
Posts: 524

Rep: Reputation: 37
I disagree. You shouldn't need to upgrade alsa, but you will definitely need to upgrade arts, and probably qt too
 
Old 03-02-2004, 10:26 AM   #5
KMcD
Member
 
Registered: Jun 2003
Location: Dublin, Ireland
Distribution: Slack -- current
Posts: 354

Rep: Reputation: 30
I upgraded it when I had a problem with sound. Just did it to be extra careful really. qt will upgrade along with kde.

command to use is:

swaret --upgrade kde

or

swaret --upgrade kde -a

if you trust swaret. It will by default check dependancies.

Last edited by KMcD; 03-02-2004 at 10:28 AM.
 
Old 03-02-2004, 11:10 AM   #6
ferreter
Member
 
Registered: Oct 2002
Location: USA, IL
Distribution: Debian/Gentoo/Slack
Posts: 215

Original Poster
Rep: Reputation: 30
I have occasional kde crashes which seem to do w/ alsa. D'ya suppose that an alsa upgrade will solve that issue? Does anyone else here experience KDE crashes? If upgrading to 3.2 causes more of these then I'll hold off for now
 
Old 03-02-2004, 11:14 AM   #7
ferreter
Member
 
Registered: Oct 2002
Location: USA, IL
Distribution: Debian/Gentoo/Slack
Posts: 215

Original Poster
Rep: Reputation: 30
Quote:
Originally posted by KMcD
I upgraded it when I had a problem with sound. Just did it to be extra careful really. qt will upgrade along with kde.

command to use is:

swaret --upgrade kde

or

swaret --upgrade kde -a

if you trust swaret. It will by default check dependancies.
Did you have to do anything else at all for this to work or did it just install w/ no issues. If QT upgrades will that bork anything else? I hate being so hesitant but everything (pretty much) has run so well in Slack that a big package upgrade sort of scares me.
 
Old 03-02-2004, 12:54 PM   #8
Wynd
Member
 
Registered: Jul 2001
Distribution: Slackware 12
Posts: 511

Rep: Reputation: 32
Qt being upgraded shouldn't mess anything up. I've done "swaret --upgrade kde -a" and/or "swaret --install kde -a" a bunch of times and it always works fine.
 
Old 03-02-2004, 01:18 PM   #9
tobyl
Member
 
Registered: Apr 2003
Location: uk
Distribution: slackware current
Posts: 768

Rep: Reputation: 64
Make sure you have the most recent version of swaret, as there were some changes needed recently.
http://www.swaret.org/index.php
It works well, you should not have any problems, I recommend that you have dependency checking ON ( /etc/swaret.conf).
If you are really worried about hosing a good setup, backup your partitions first. Then you have a way back if you need to. I heartily endorse Partimage.
 
Old 03-02-2004, 02:04 PM   #10
ferreter
Member
 
Registered: Oct 2002
Location: USA, IL
Distribution: Debian/Gentoo/Slack
Posts: 215

Original Poster
Rep: Reputation: 30
So can I use swaret to update swaret?
 
Old 03-02-2004, 02:35 PM   #11
Minderbinder
Member
 
Registered: Aug 2003
Location: Boston, MA
Distribution: Slackware-current
Posts: 142

Rep: Reputation: 15
Quote:
Originally posted by ferreter
So can I use swaret to update swaret?
You can if you remove swaret from the line
EXCLUDE= lilo swaret
in swaret.conf
 
Old 03-03-2004, 05:58 AM   #12
KMcD
Member
 
Registered: Jun 2003
Location: Dublin, Ireland
Distribution: Slack -- current
Posts: 354

Rep: Reputation: 30
I had only one problem initially due to using an older version of swaret which did not do a complete dependancy check for some reason. The commands I used were:

swaret --update

swaret --upgrade kde -a
swaret --upgrade gcc -a
swaret --upgrade lib -a
swaret --upgrade alsa -a
swaret --upgrade arts -a

It now works perfectly on my pc.

I upgraded the lib packages due to the initial dependancy problem, should not happen with the current version of swaret.
 
Old 03-03-2004, 09:18 AM   #13
ferreter
Member
 
Registered: Oct 2002
Location: USA, IL
Distribution: Debian/Gentoo/Slack
Posts: 215

Original Poster
Rep: Reputation: 30
Hmmm... Is there any special configuration needed for swaret to get access to kde? It comes up as an unfound package. I tried to add some rsync sites to the config file but I don't have rsync availible. (Did not install it from source as of yet, but will do just that if it fixes the issue). I did also change swaret to be for the "current" distro and not 9.1 but that didn't make a difference. Oh, and I also did a swaret --update and that didn't fix the problem either. I must be missing something trivial as other packages were able to be installed using swaret (but not many have ever been availible).
 
Old 03-03-2004, 09:49 AM   #14
EyesOnly
Member
 
Registered: Aug 2003
Location: The Netherlands
Distribution: SlackWare
Posts: 202

Rep: Reputation: 30
You can download Slackware packages from http://www.kde.org/download/ (scroll down till you find Slackware, they are available for 8.1,9.0 and 9.1)

I installed these packages, and all works fine now.

And if it's worth it? I would say definitely. KDE 3.2 is so much nicer that 3.1
it is faster(and not a little faster, REALLY faster), it looks cleaner(options are cleaned up and arranged more logically), and it looks better.(love the plastic theme )
And I didn't noticed any more crashes than whit 3.1 I even have the idea that 3.2 is more stable than 3.1.

and installing is easy, so why not give it a try? it's worth it.
 
Old 03-03-2004, 11:09 AM   #15
KMcD
Member
 
Registered: Jun 2003
Location: Dublin, Ireland
Distribution: Slack -- current
Posts: 354

Rep: Reputation: 30
I'm stumped as to what the problem could be. Below is my swaret.conf file. See if that helps. Ignore the version number.


############################################################
#
# swaret.conf, Version: 1.6.1
#
### /etc/swaret.conf - SWARET EXAMPLE CONFIGURATION FILE ###
#
# Define a valid Slackware Linux Version.
# (Used for Dependency Support and other Features)
#
# NOTE: If you want to use Slackware Linux Current,
# set VERSION to 'current' (VERSION=current).
#
VERSION=current
#
#
#
# Define Slackware (8.1 or Higher or Current) Linux Mirrors.
# (Used for Official Slackware Linux Packages)
# (Slackware Linux Mirrors available at http://www.slackware.com)
#
# Syntax: ROOT=PROTOCOL:URL
#
# NOTE: swaret will use the order of the specified ROOT URL's.
#
#ROOT=file:/mnt/cdrom
#ROOT=file:/mnt/dvdrom
#ROOT=file:/mnt/usbmemstick
#ROOT=ftp://ftp.nluug.nl/pub/os/Linux/distr/slackware/slackware-current
ROOT=http://sunsite.cnlab-switch.ch/ftp/mirror/slackware/slackware-current
ROOT=ftp://ftp.slackware.no/pub/linux/slackware/slackware-current
ROOT=http://www.slackware.no/slackware/slackware-current
ROOT=ftp://ftp.slackware.at/slackware-current
ROOT=http://www.slackware.at/data/slackware-current
ROOT=ftp://ftp.planetmirror.com/pub/slackware/slackware-current
ROOT=http://ftp.planetmirror.com/pub/slackware/slackware-current
#ROOT=rsync://rsync.slackware.no/slackware/slackware-9.0
#ROOT=rsync://rsync.slackware.at/slackware/slackware-9.0
#ROOT=file:/pub/slackware
#ROOT=file:/mnt/nfsshare/slackware
#ROOT=file:/mnt/sambashare/slackware
#
#
#
# Define Repository URL's with Slackware Linux Packages.
# (Used for Repository Slackware Linux Packages)
# (Repository URL's available at http://www.swaret.org/?menu=sp)
#
# NOTE 1: To use a Local Repository or Remote Repository,
# be sure it contains the following Files:
# - CHECKSUMS.md5 (For MD5 Sum, REQUIRED)
# - FILELIST.TXT (For Package Name + Size, REQUIRED)
# - PACKAGES.TXT (For Package Description, NOT REQUIRED)
# - MANIFEST.bz2 (For Dependency Support, NOT REQUIRED)
# NOTE 2: To create your own Repository, use 'swaret-tools'.
# You can get 'swaret-tools' at http://www.swaret.org!
#
# Syntax: REPOS_ROOT=REPOSITORYNAME%PROTOCOL:URL
#
# NOTE 1: The REPOSITORY NAME can only be ONE Keyword!
# NOTE 2: swaret will use the order of the specified REPOS_ROOT URL's.
#
#REPOS_ROOT=LinuxPackagesDOTNET%ftp://ftp.linuxpackages.net/pub/Slackware-9.1
#
#REPOS_ROOT=My_Slackware_Packages_On_CD-ROM%file:/mnt/cdrom
#REPOS_ROOT=My_Slackware_Packages_On_DVD-ROM%file:/mnt/dvdrom
##REPOS_ROOT=BlazeBox%http://users.lichsnel.nl/pub/slackware
##REPOS_ROOT=CuoreDOTORG%http://heart.core.org/packages.slackware
##REPOS_ROOT=LinuxPackagesDOTNET.FTP%ftp://ftp.linuxpackages.net/pub/Slackware-9.1
##REPOS_ROOT=LinuxPackagesDOTNET.HTTP%http://www3.linuxpackages.net/Slackware-9.1
##REPOS_ROOT=SlackPack%http://www.slack.it/slackpack
#REPOS_ROOT=My_Slackware_Packages_On_USB_Memory_Stick%file:/mnt/usbmemstick
#REPOS_ROOT=SomeRemoteRepository%ftp://ftp.someremoterepository.net/s.../slackware-9.1
#REPOS_ROOT=SomeRemoteRepository%http://www.someremoterepository.net/.../slackware-9.1
#REPOS_ROOT=SomeRemoteRepository%rsync://rsync.someremoterepository.net/slackware/slackware-9.1
#REPOS_ROOT=MyLocalRepository%file:/pub/myrepos"
#REPOS_ROOT=MyRemoteRepository_Using_NFS-Share%file:/mnt/nfsshare/slackware
#REPOS_ROOT=MyRemoteRepository_Using_Samba-Share%file:/mnt/sambashare/slackware
#
#
#
# Define Libraries (8.1 or Higher or Current) List Mirrors.
# (Used for Dependency Support)
#
# NOTE 1: You need to specify a Libraries List Mirror which
# contains a 'libraries-VERSION' File.
#
# NOTE 2: To create the Libraries List, use 'swaret-tools'.
# You can get 'swaret-tools' at http://www.swaret.org!
# You can also clear all DEP_ROOT Variable(s) which will
# allow swaret to create the Libraries List for you
# during Dependency Check using the defined ROOT Variable(s) above.
#
# Syntax: DEP_ROOT=PROTOCOL:URL
#
# NOTE: swaret will use the order of the specified DEP_ROOT URL's.
#
#DEP_ROOT=file:/mnt/cdrom
#DEP_ROOT=file:/mnt/dvdrom
#DEP_ROOT=file:/mnt/usbmemstick
DEP_ROOT=http://www.swaret.org/swaret
DEP_ROOT=ftp://ftp.swaret.org/swaret
#DEP_ROOT=rsync://rsync.swaret.org/swaret
#DEP_ROOT=file:/pub/swaret
#DEP_ROOT=file:/mnt/nfsshare/swaret
#DEP_ROOT=file:/mnt/sambashare/swaret
#
#
#
# swaret Settings
#
# Do you want swaret to use Random Slackware Linux Mirrors?
# -> 1 for yes, 0 for no.
#
RANDOMR=0
#
#
#
# Do you want swaret to parse all the Package Descriptions?
# -> If set to 1, swaret will also match Packages whose Description
# is matching the Keyword(s) you specify after --ACTION.
# NOTE: swaret will parse all the Package Descriptions for this,
# and might slow down swaret when using an older System.
# -> If set to 0, swaret will not use Package Descriptions
# to match one or more Packages.
#
USEPKGDESC=0
#
#
#
# If you don't want swaret to Upgrade, Install, Re-Install, Download,...
# some Packages, add the KEYWORDS to the EXCLUDE Variable.
# To disable Exclude Method: swaret --exclude -off
# To enable Exclude Method: swaret --exclude -on
#
# NOTE: You can add ANY EXTENDED REGEXP (Regular Expression) to the EXCLUDE Variable(s)
#
# Basic Exclude
#
EXCLUDE=kernel
EXCLUDE=lilo swaret
EXCLUDE=MANIFEST.bz2$
EXCLUDE=.*dl$ .*PACKAGER$ .*MYBUILD$

#
# Advanced Exclude
# Syntax: KEYWORD[DONT_EXCLUDE_ME_KEYWORD1,DONT_EXCLUDE_ME_KEYWORD2,...]
# Example: kde-i18n[nl,en_GB] koffice-i18n[nl,en_GB]
#
EXCLUDE=kde-i18n[nl,en_GB] koffice-i18n[nl,en_GB]
#
#
#
# Do you want to enable Dependency Check?
# -> If set to 1, swaret will start the Dependency Check after
# every Upgrade, Install and Re-Install Procedure.
# -> If set to 0, swaret will not start the Dependency Check
# after any Procedure.
#
DEPENDENCY=1
#
#
#
# Do you want swaret to Search for missing Libraries (and Fix)
# which could be found on your System, but not tracked by ldconfig?
# -> 1 for yes, 0 for no.
#
DSEARCHLIB=1
#
#
#
# Set to 1, if you want swaret to use the 'slocate' program
# to Search for missing Libraries.
# (be sure to issue the 'updatedb' Command regularly!)
# If DSEARCHM is set to 0, swaret will use
# the 'find' program to locate missing Libraries.
# -> 1 for yes, 0 for no.
#
DSEARCHM=1
#
#
#
# Start MD5 Check after Fetching Packages, Patches and Sources?
# -> 1 for yes, 0 for no.
#
MD5CHECK=1
#
#
#
# Start GPG Signature Check after Fetching Packages, Patches and Sources?
#
# NOTE: Check out F.A.Q. (--faq gpg) how to Import a Public GPG Key which
# will be used by the GPG Signature Check.
#
# -> 1 for yes, 0 for no.
#
GPGCHECK=0
#
#
#
# Show Description for Packages during
# Upgrade, Install, Re-Install,... Procedures?
# -> If set to 0, you will not see a Description.
# -> If set to 1, you will see a Description.
#
DESC=0
#
#
#
# Cache Directory for (Repository) Packages and Sources.
#
CACHE_DIR=/var/swaret
#
#
#
# Enable Logging?
# -> 1 for yes, 0 for no.
#
LOG=1
#
#
#
# swaret Log File
#
LOG_FILE=/var/log/swaret
#
#
#
# Show Warnings?
# -> 1 for yes, 0 for no.
#
WARNINGS=1
#
#
#
# Show Information?
# -> 1 for yes, 0 for no.
#
INFORMATION=1
#
#
#
# Network Settings
#
# Network Interface
# Use this if you have a Network Interface.
#
NIC=eth0
#
#
# Local Interface
# Use this if you do not have a Network Interface.
#
# For Example (CD-ROM):
# You got a Slackware Linux CD-ROM,
# mount the CD-ROM to /mnt/cdrom and
# set ROOT to 'file:/mnt/cdrom' in /etc/swaret.conf.
# Also, set NIC to 'lo' (Local Loop Device).
#
# NIC=lo
#
#
#
# Progress
# If set to 0, swaret will use the '%' Download Interface.
# If set to 1, swaret will use the 'size' Download Interface.
# If set to 2, swaret will use the 'wget/rsync' Download Interface.
#
PROGRESS=1
#
#
#
# Timeout for wget and/or rsync.
# -> Number of seconds for Timeout
#
TIMEOUT=35
#
#
#
# Retries for wget and/or rsync.
# -> Number of Retries
#
RETRIES=5
#
#
#
# Behind a Firewall? Using FTP Mirrors?
# -> 1 for yes, 0 for no
#
PASSIVE_FTP=1
#
#
#
# If you want HTTP or FTP Proxy Support,
# uncomment and Setup the following Variable:
#
# WGET_PROXY=http://IP or HOST:PORT
#
#
#
# If you want RSYNC Proxy Support,
# uncomment and Setup the following Variable:
#
# RSYNC_PROXY=IP or HOST:PORT
#
### /etc/swaret.conf - SWARET EXAMPLE CONFIGURATION FILE ###
 
  


Reply



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
KDE 3.4.1, Is it worth it? justin_p Slackware 13 07-01-2005 06:56 PM
Is upgrading to X11 8.6.1 worth it? DreameR-X Slackware 5 12-18-2004 08:24 PM
Compile KDE=worth the trouble? dhave Slackware 8 11-08-2004 04:00 PM
10.1 worth upgrading? WLAN PCMCIA questions... lostchild Mandriva 3 09-19-2004 12:18 AM
Worth upgrading? r_jensen11 Slackware 2 09-06-2003 11:30 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 06:45 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration