Updating custom packages - best practices
As may many already know, Slackware is a superb disto. It has a good base of most common server & desktop applications in well prepared packages you can rely on. On the other (darker) side the collection is relatively small and somebody may found it even unsatisfactory and is forced to install 3rd party packages or build his own. Process of custom package creation in Slack is very straightforward and with proper written SlackBuild script very very easy.
The annoyance comes with tracking of (security) updates. My question is, how do you do that ? Did you successfuly automated this mechanism with updated package as the final product or are you just checking security e-mails, mailing lists or other sources of security advisories and manualy build an updated version ?
Last edited by dunric; 01-10-2006 at 08:21 AM.