Just a matter of curiosity!
Does anyone else use slackpkg and do the slackware upgrade process in the (old fashioned way)?
As said, nothing against slackpkg, just curiosity.

Basically going to the repository, reading the changelog and getting the Patches/
Tell me a little more about it, what's your technique to do...
And what are the advantages over the more "automated" method?

I've used slackpkg for quite a while. I have manually applied packages in the past, nothing wrong with that. If you're running -current then manually applying updates becomes too much work. Yes, it's always a good idea to read the changelog in the event that an application needs attention after an update.

1 members found this post helpful.

When I ran 14.2, I used GSlapt.

Until recently (2-3-4 years ago) I did everything manually by reading the changelog. At some point I decided to try slackpkg and was well pleased with it so began to use it on local machines. I still read over the change log before using it, so I know what to expect, and I tend to schedule slackpkg uodate sessions every couple of weeks as opposed to tracking all changes closely.

On remote systems I still do everything manually and more selectively.

I read the change log and do it manually.
is your friend.

1 members found this post helpful.

I still update manually. Nothing against slackpkg, just that doing by hand is mostly pretty easy. I also run stuff from SBO and packages I have built myself so I want to avoid surprises. It seems like updating the black list would be as much effort.

I have one old 32bit X86 laptop (Thinkpad X60) I'm using to test Slackware -current as Slackware is one of the few distributions (along with Debian) that has 32 bit as a full featured supported target. Apart from mesa not liking the old Intel integrated graphics (so falling back to llvmpipe) no big issues.

I use rsync to synchronise the (binary) Slackware tree from my local mirror, then upgradepkg, packages first then the kernel after (I'm lazy and just use huge-smp)

Then I copy the tree as slackware-yyyymmdd so that I can roll back at any time by using upgradepkg in the dated tree. I keep three or four old trees (320Gb mechanical hard drive).

On the release machines (15.0 and 14.2) I just use slackpkg.

Ditto, I use slackpkg regularly.
No issues there.

I used to stick to pkgtools for all my package needs. I later picked up using slackpkg and liked it. After adding slackpkg+ to the mix, there is no going back. I still use installpkg, upgradepkg and removepkg. The first two after upgrading or rebuilding a package using a SlackBuild script and especially when rebuilding/upgrading or adding several packages (dependencies). Once done with that process I then rebuild my local repository's meta data. I use installpkg when installing new kernel packages, removepkg for removing no longer used kernel packages. The upgradepkg option oldpackagename%newpackagename comes in handy.

I use slackpkg everything ok for me

Same here.

Yes, that's what drove me to write the first version of my "slackscan" script. At the time slackpkg+ didn't exist, so there was no way to join multiple sources of packages together in slackpkg.

I don't follow current any more, but I still use my scripts to keep my Slackware 15.0 partition updated.

2 members found this post helpful.

I did follow -current for many years. Not anymore. I've become comfortable and I like the stability of 15.0.
I get my bleeding-edge fix from Void.

1 members found this post helpful.

I use slackpkg. I wrote a little script to make it easier:

Full disclosure: The script was not my idea. The idea was described by a member of my LUG shortly after I moved to these parts.

1 members found this post helpful.

For some cases that building packages from source, the most commands used are "makepkg,removepkg,installpkg".
Usually, slackpkg is encough for daily update.