I use limited swaret functionality.

I will check the changelog,

Then upgradepkg manually. Depending on the packages. Some critical system packages, I will drop the system to init level 1
before upgradepkg.

I use slackpkg upgrade-all
Till now, I never had a problem with that
(Of course I read the ChangeLog before any update )

Will slackpkg downgrade the package? Such as when udev was downgraded.

I don't know, I blacklisted udev package in slackpkg blacklist config
when it was reported to have problem

But slackpkg is able to downgrade a package, I experienced that
when I installed the current slackpkg package from the slackpkg site
and it was downgraded as the slackpkg package from mirrors was
older (I fixed that with blacklist slackpkg).

Now as udev works and slackpkg is up to date in the mirrors,
I un-blacklisted them

Has Debian actually moved beyond the 2.2 kernel yet? :P

No problems using Swaret on two machines.

Just read the changelog and blacklist the items mentioned here.

swaret & changelog. Though I have on occasion not first checked the changelog and ended up having a lot of fun.

I voted Other.
I like to compile from source then use checkinstall to make a Slackware package (so it can be later removed cleanly).

When a security update comes out for 10.1, I just grab it off the Slackware site and upgradepkg. A few packages here and there is not hard to update. As for -current, I use just a few packages (Firefox, Thunderbird, jre-symlink, Fluxbox, K3b) so there's no reason to use swaret, slapt-get or anything else but the ChangeLogs and upgradepkg.

MagicMan

IMO Slackpkg is much better than either Swaret or Slapt-get.
It is simple, effective, and always dependable.

The only thing lacking from slackpkg is a support for repositories like linuxpackages

I use slackpkg to download packages, then I install everything manually. I've never had a problem with it yet. It's basically a download tool for me, that's it.

I love how well split this is.

at the moment it's perfectly split three ways. I had figured that swaret and slapt-get would be close to each other but I never noticed how many people used slackpkg or did it manually.

No, IIRC swaret was removed due to swaret's former author's very bad behaviour, not because of the program itself. The troublesome author left the project shortly after the "incident" that caused PV to take swaret out of the distro.

i dont update packages, i just installed stable version and pach it if needed
%just for some comments plz
mkoljack wrote
u could have get a stable version, why u go for current and blame slackware if u dont have the mind to maintain

npaladin2000 wrote
who told slack is not slipped with these updating softs... tehy r 3rd party softs, use with ur risk

but u dont have 2 use slack with risk it is perfect, ultimate linux

what i know is I have the (somewhat) most fresh new packages than any other distro.. tht too with my stable version

without using slack these guys are commenting leave them