Slackware This Forum is for the discussion of Slackware Linux.
|
Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
 |
02-01-2006, 05:55 PM
|
#1
|
Member
Registered: Aug 2004
Distribution: Slackware current
Posts: 250
Rep:
|
KDE 3.5.1 slackbuild?
Does anyone have or know where i can get my hands on a KDE 3.5.1 slackbuild? I have the packages but I like building them.
|
|
|
02-01-2006, 06:02 PM
|
#2
|
Member
Registered: Aug 2004
Location: Aguascalientes, AGS. Mexico.
Distribution: Slackware 13.0 kernel 2.6.29.6
Posts: 816
Rep:
|
there you go
I used this one
taken from here
|
|
|
02-01-2006, 06:05 PM
|
#3
|
Senior Member
Registered: Mar 2003
Location: Seattle
Distribution: Slackware ?-14.1
Posts: 1,029
Rep:
|
i would be careful upgrading kde with a package that isn't released by Patrick or slackware itself. kde can be compiled many different ways, you never know what may or may not work after you upgrade
|
|
|
02-01-2006, 06:09 PM
|
#4
|
Member
Registered: Aug 2004
Distribution: Slackware current
Posts: 250
Original Poster
Rep:
|
Quote:
Originally Posted by raska
|
I said I already had the packages. I also have the source but I'm looking for the .Slackbuilds
|
|
|
02-01-2006, 06:32 PM
|
#5
|
Member
Registered: Aug 2004
Location: Aguascalientes, AGS. Mexico.
Distribution: Slackware 13.0 kernel 2.6.29.6
Posts: 816
Rep:
|
Quote:
Originally Posted by bird603568
I said I already had the packages. I also have the source but I'm looking for the .Slackbuilds
|
sorry, I missunderstood .... can't help you with the .Slackbuild files
maybe googling around
Last edited by raska; 02-01-2006 at 06:33 PM.
|
|
|
02-01-2006, 06:45 PM
|
#6
|
Member
Registered: Jan 2004
Location: Poland, Poznan
Distribution: Slackware current 32 / 64
Posts: 433
Rep:
|
My way
1. Copy a KDE 3.4.2 complete tree structure [with files] from a source section of the ftp.slackware.com site.
2. Change the version number to 3.5.1 inside the top-level script named "kde.SlackBuild".
3. Insert every KDE 351 component source file [from kde.org] into appr. subdirectory.
4. Delete all files in subdirs with "diff" or "patch" in its name - we won't be patching anything.
5. Make sure all scripts are executable /adjust file permissions when needed/
6. Make sure you have at least 3 GB of Hdd free space and appr. 20+ hours to compile KDE.
7. Log out of Kde and X -> relogin as root -> removepkg your older KDE component packages.
8. Run main kde.SlackBuild script. Watch the screen while processing - if errors occurs something must be corrected... I had to small Hdd space...
9. Go somewhere ... for sleep for example.
10. Happy end of this process results in NEW fresh KDE tgz packages sitting (I hope I remember correctly) in /tmp directory. You must run installpkg all of them as root.
That worked for me while compiling Kde 350.
BUT I cannot guarantee I remember everything perfectly....do it on your own risk :-)
Remember to remove all unpacked source files [in /tmp] except your fresh TGZ packages !
|
|
|
02-03-2006, 10:29 AM
|
#7
|
Member
Registered: Jan 2004
Location: Poland, Poznan
Distribution: Slackware current 32 / 64
Posts: 433
Rep:
|
Correction
Sorry I made some errors at my previous post (I was sleepy).
This procedure should be correct.
1. Copy a KDE 3.4.2 complete tree structure [with files] from a source section of the ftp.slackware.com site. Remove older KDE342 *.tar.bz2 source files from subdirectories.
2. Insert every KDE 351 source file [from kde.org] into appr. subdirectory.
3. Change the KDE version number to 3.5.1 inside the top-level option file named "KDE.options". Do it that way in all subdirectories containing "local.options" file via editing that file. Version number can be different (Kdevelop , Koffice) but should match appropiate source KDE component package's version number.
4. Delete all files in subdirs with "diff" or "patch" in its name - we won't be patching anything now.
5. Make sure all scripts in top- and subdirs are executable /adjust file permissions when needed/
6. Make sure you have at least 3 GB of Hdd free space and appr. 20+ hours to compile KDE.
7. Log out of Kde and X -> relogin as root -> removepkg your older KDE component packages except Qt package.
8. Run main KDE.SlackBuild script. Watch the screen while processing - if errors occurs something must be corrected... I had too small Hdd space...
9. Go somewhere ... for sleep for example.
10. Happy end of this process results in NEW fresh KDE tgz packages sitting in /tmp directory. The new packages are actually installed by Slackbuild scripts.
That worked for me while compiling Kde 350.
BUT I cannot guarantee I remember everything perfectly....do it on your own risk :-)
Remember to remove all unneeded source files [in /tmp] except your fresh TGZ packages !
|
|
|
02-04-2006, 12:35 AM
|
#8
|
LQ Newbie
Registered: Sep 2005
Distribution: Slackware
Posts: 25
Rep:
|
|
|
|
All times are GMT -5. The time now is 01:56 PM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|