Slackpkg?
This is the third time I'm installing Slackware, folks. After a hiatus, I'm back! :D
Anyway, this time I've decided to ditch swaret or slapt-get as reliable means of updating the system. Instead I've decided to go with slackpkg and using only official updates and the changelog. It seems to be a breeze to use... So what are the things to watch out for, particularly with reference to upgrades (apart from reading and following the changelog of course)? |
You already answered your own question. Changelogs. I've been using slackpkg for a long time to stay abreast with -current and have had no problems at all.
I use the slackpkg blacklist command to blacklist those things like the kernel, headers, and such that I don't want it to touch. |
Hokay, chief. :)
I'm also impressed by Checkinstall (which I use in Debian to install packages not found in the repositories) and it's pretty impressive for the occasional custom package. |
Is there a gui for slackpkg? Now that I'm comfortable enough with Slackware, I want to start doing updates on a regular basis. Thanks.
|
I don't know of any gui but I want to reiterate about reading the changelog before doing an upgrade. It's v important.
You could set up a cron job to check the changelog daily and go by that if you need to upgrade or not. This is what I do. My crontab is: Code:
0 6 * * * /usr/bin/aterm -fn sabvga -e /home/dave/scripts/changelog 1>/dev/null 2>&1 Code:
#!/bin/bash slackpkg update slackpkg upgrade-all |
Checkinstall is awesome for a paranoid source-builder like me who doesn't feel like writing SlackBuilds or .tgz's.
|
*Edit: Seems the version of slackpkg in -current (2.05 I think) has a curses gui now.
|
Yeah, the new one in current is curses based. Freaked me out the first time I ran it LOL
|
Cool! Thanks. this thread is becoming very informational. I think as long as it's kept on topic, it could become a great resource for future reference. :twocents:
|
I wouldn't recommend updating to current now though. Updating from 10.2 is likely to cause problems. It did when I tried it.
|
You're right, upgrading now would be painful. If you've got a real itch to be at -current though and have a box you can run a new install on...
You can run a local slackware -current mirror using rsync with Alien Bob's script from http://www.slackware.com/~alien/tool...are-current.sh which also creates the install CDs/DVD. Once you have them... :) |
I'm currently pointing to 10.2. Will upgrade only when 11.0 comes out.
|
You don't need Slack-11 erh.. Slack-current to run the latest Slackpkg, you can grab the latest version at http://slackpkg.sourceforge.net/
|
I wasn't referring to slackpkg. I was just referring to Slackware packages in general.
|
All times are GMT -5. The time now is 08:25 PM. |