Script to display obsolete distfiles (sbopkg)

lems · 07-03-2015, 07:04 AM

Hello,

I wrote this rather silly script a few days ago; it will display distfiles that are most likely outdated. It does not remove them, one could pipe its output to xargs, though. I wrote this for my own build tool, but thought that a sbopkg version would be useful as well.

Here it is:
https://gist.github.com/1ems/80e82c42bfbca70280cd

ponce · 07-03-2015, 07:10 AM

do you know of the sbopkg's command line option "-o"?

Code:

-o   List the currently installed cached source files which are deemed obsolete,
     and optionally delete them.

     Source files are obsolete when no .info file's DOWNLOAD field(s) reference it
     any more, which is something that can happen after syncing the local repository.

     Please  note  that  only the currently active repository is used to identify the
     obsolete sources, so if the user builds packages with different repositories
     (e.g., for different Slackware versions) the source files only used in the
     ``other'' repository will be listed.

lems · 07-03-2015, 08:27 AM

Oops, no, I wasn't aware of that option, should have looked closer at sbopkg, I guess; now I made a fool out of myself.

Please disregard this then, sorry!

bormant · 07-03-2015, 08:39 AM

sbopkg has an interactive mode menu command too: Utilities -> Obsoleted sources.

Richard Cranium · 07-03-2015, 10:33 PM

Quote:

Originally Posted by lems

Oops, no, I wasn't aware of that option, should have looked closer at sbopkg, I guess; now I made a fool out of myself.

Please disregard this then, sorry!

You should compare the script that you wrote with the way that sbopkg does it. Maybe your way is better. If it isn't, you'll learn something from comparing what you did with what they did.

lems · 07-04-2015, 12:20 AM

Quote:

Originally Posted by Richard Cranium

You should compare the script that you wrote with the way that sbopkg does it. Maybe your way is better. If it isn't, you'll learn something from comparing what you did with what they did.

Yes, I had a look at the code, and I don't think my script is any better. sbopkg's code is very well-written and it gave me some ideas, quoting the paths might be a good idea (though I sometimes have trouble understanding some of it as I'm only a beginner when it comes to shell programming and those kinds of things ...). As bormant wrote, sbopkg even has a dialog interface for this (and a progress bar). (From what I understand, sbopkg reads every .info file, while my script iterates over every SBo package installed. This would mean that the sources of a package that is no longer installed would be displayed as obsolete by my script.) Oh well, at least I had some exercise.

Gerard Lally · 07-04-2015, 02:01 PM

Quote:

Originally Posted by lems

I sometimes have trouble understanding some of it as I'm only a beginner when it comes to shell programming and those kinds of things ...

From my own amateur's perspective I thought the script was a worthy effort.

lems · 07-05-2015, 07:47 AM

Quote:

Originally Posted by gezley

From my own amateur's perspective I thought the script was a worthy effort.

Thank you, gezley. I did learn quite a bit about shell programming and its commands by writing my own package manager and SlackBuilds.org build tool during the last two years. (I hope someday I might be able to learn a real scripting language like python, perl or ruby.)