Welcome to the most active Linux Forum on the web.
Go Back > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Slackware This Forum is for the discussion of Slackware Linux.


  Search this Thread
Old 07-27-2008, 02:50 AM   #1
Registered: Apr 2007
Posts: 63

Rep: Reputation: 15
how do you keep packages that you install up to date and patched?

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?
Old 07-27-2008, 02:57 AM   #2
Amigo developer
Registered: Dec 2003
Location: Germany
Distribution: Slackware
Posts: 4,890

Rep: Reputation: 569Reputation: 569Reputation: 569Reputation: 569Reputation: 569Reputation: 569
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.
Old 07-27-2008, 05:42 AM   #3
Registered: Nov 2005
Location: Diessen, The Netherlands
Distribution: Slackware 14.2
Posts: 670

Rep: Reputation: 38
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.
Old 07-27-2008, 06:15 AM   #4
Registered: Apr 2007
Posts: 63

Original Poster
Rep: Reputation: 15
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?
Old 07-27-2008, 08:15 AM   #5
Senior Member
Registered: Oct 2003
Location: Northeastern Michigan, where Carhartt is a Designer Label
Distribution: Slackware 32- & 64-bit Stable
Posts: 3,541

Rep: Reputation: 1060Reputation: 1060Reputation: 1060Reputation: 1060Reputation: 1060Reputation: 1060Reputation: 1060Reputation: 1060
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?
Old 07-27-2008, 11:44 AM   #6
Senior Member
Registered: Oct 2005
Location: New Mexico
Distribution: Slackware
Posts: 1,623

Rep: Reputation: Disabled
Originally Posted by Unregistered View Post
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?
Simply build a new package and install it with "upgradepkg"

Old 07-27-2008, 02:53 PM   #7
Senior Member
Registered: Oct 2005
Distribution: Slackware 14.1
Posts: 3,482

Rep: Reputation: 544Reputation: 544Reputation: 544Reputation: 544Reputation: 544Reputation: 544
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.
Old 07-27-2008, 10:15 PM   #8
Registered: Apr 2005
Location: Colombia
Distribution: Slackware 14.2
Posts: 82

Rep: Reputation: 18
I use mostly Slackbuilds from 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

Last edited by Pratt; 07-27-2008 at 10:16 PM.


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off

Similar Threads
Thread Thread Starter Forum Replies Last Post
Need a script to remove packages by date samac Slackware 3 07-21-2008 08:33 AM
List packages WITH install date? ranger_nemo Ubuntu 4 02-21-2008 05:51 PM
Tracing Installed date of systems and packages Swakoo Linux - General 1 08-29-2006 07:16 AM
OpenBSD - no up to date mozilla packages uselpa *BSD 7 05-08-2006 03:32 AM
Debian Packages (apt-get) not up-to-date? rmdl Debian 12 02-23-2004 08:59 AM > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 12:56 PM.

Main Menu
Write for LQ is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration