I mean packages that are not in the official slackware repository which aren't maintained or patched with bug fixes/security fixes by Pat; i.e. those packages that you create yourself whether through src2pkg, paco, checkinstall, ./configure make make install, makepkg or other such software.

What if you have numerous such packages, how does one go about automating the update/patches of such packages efficiently?

Some projects have a notifiction service where you can register to receive an e-mail or RSS feed when new versions become available. Otherwise you just have to regularly visit the softwares' home page to stay on top of updtes.

Not completely 100% full proof, but you can register for the Slacky-eu RSS feeds.
When there are new versions they usually pop up pretty quickly there.

perhaps this might be a silly question but how does one go about patching security/bug fixes when i have already used the source to create a package(not from official repositories) and installed it using pkgtool?

I could be off base here but it seems to me that every piece of software I've ever worked with includes version number changes when something, you know, changes. The software I have added all seems to follow that convention (pretty much all of it appears to be in CVS and every time you commit something in CVS you get a version change). So, it's a simple task to just download the tarball (or use CVS), build the thing, and use upgradepk to upgrade the previously-installed version. Since checkinstall went away, I've been using src2pkg to build software packages and, so far, works just fine for keeping things up to date.

So, once you've got the "official" update, just build it and use upgradepkg --reinstall to keep your package log current?

Simply build a new package and install it with "upgradepkg"

Brian

A couple of months ago we had a discussion about tracking non-stock Slackware packages.

I use such a script to track my third-party packages.

Generally, however, if a non-stock package is critically important to me, usually I am aware when new sources are available. I don't subscribe to any feeds or the like. I just watch the various GNU/Linux news headlines. Routinely, I see updates posted or something that reminds me to check for updates. If I trip over a bug or quirk I might then look for new source packages. Then, because I use SlackBuild scripts, I create a new package and install. I have no need for cutting or bleeding edge packages and this approach satisfies me.

I use mostly Slackbuilds from Slackbuilds.org and Alien's Repository.

They both keep track of their changes in a Changelog.txt. I wrote a really basic basic Script that lists my third party packages. It dowloads both of the Changelogs and then compares them with my list of packages and prompts me which packages should be upgraded.

After that it stores the changelogs, and next time I run the script it will do a simple "diff" between the old and new Changelogs, so i can always be up to date.

I run it every now and then