Certainly. I have a slow connection, and it took me 37 hours to download the Slackware 13.37 DVD iso image via torrent. I surely sympathize with the OP if that's his case as well.

to add to my post to go from 12.2 also need the following after "slackpkg update tgz" slackpkg install tgz

The OP could also opt for downloading CDs 1-3 via torrent which will give a full install (that is a smaller download).

Not to start a new thread I'll ask here.

Let's imagine that we have a Slackware system with some packages installed from SlackBuilds.org.
Then a new release is ready and we upgrade our system.
The next step is to download the new slackbuilds for those packages and upgrade them?

It seems pretty clear but still and all I decided to ask a question. Maybe some specific problems may occur?

Best regards,
Alexey

If the software works for me, I do not upgrade, but if I find some
problem, then upgrade ...

As far as I can see you'll have to look at the dependencies.

The Slackbuilds don't recognize the Slackware-version, but if packages depend on each other and one of them has been changed in the Slackware-install you may possibly have to rebuild the packages.

Markus

From my experience the good people at slackbulds.org do an excellent job keeping up with the stable branch, that is, when a new release of slackware comes out the build scripts at slackbuilds.org are quickly updated to be in alignment with the new release. I've also found that I can frequently run older SBo packages on a newer system without problems as there is a good amount of backwards compatibility. When a package stops working due to a changed dependency you can easily deal with that on a case by case basis and build a new package, and or install a new needed dependency.