[Slackbuilds-users] Very simple way of finding dependency

Habs gen-bch at useyouresp.org.uk
Thu Sep 14 09:16:27 UTC 2017

On Wed, 13 Sep 2017 16:06:54 +0100
David Spencer <baildon.research at googlemail.com> wrote:

> Chris Willing's tool hoorex will find "inverse dependencies" of
> packages. https://github.com/cwilling/hoorex
> One other idea for finding why you installed a library -- you can list
> the files in /var/log/packages sorted by time (ls -lt) which will show
> you the other packages that were installed immediately afterwards.
> Twenty years ago I wrote this kind of thing in a little book. Ten
> years ago I used dokuwiki. Now I just never uninstall them.
> There is no official test build system that would have a full listing
> of files. Unofficially, I build almost every package from time to
> time. A list of files (depending on random options) in almost every
> package is 325 Mb. I'm not sure I would want to put them unofficially
> on a website somewhere if each query will grep 325Mb of data. (And
> also I hate elasticsearch.)

Im likely comparatively poor at sysadmin, but my approach re:slackware
taken from my old school a long time is to create (and try to maintain
haha) a register of any software added afterwards...inc documenting the
dependencies etc.

Its only a simple xml affair that records whats listed on SBo as
required and optional (if ive intalled the optional stuff) etc, but i
can cross check stuff easily enough.

My biggest problem is laziness in keeping up to it :-)

Of course this is all no good, if its not done right from the get go.

As mentioned above though, I find the var/log/packages thing can get me
some way.

I like Slackware and SBo - I think the community is great and thanks to
everyone involved keeping it ie. Slackware and SBo, as it is. If it went
full-on like the other distros, it would be a shame.

Have a lovely day folks. Peace best wishes


More information about the SlackBuilds-users mailing list