[Slackbuilds-users] Very simple way of finding dependency

Didier Spaier didier at slint.fr
Wed Sep 13 17:24:04 UTC 2017

Le 13/09/2017 à 18:12, Sebastian Arcus a écrit :
> On 13/09/17 15:29, Didier Spaier wrote:
>> Le 13/09/2017 à 12:40, Sebastian Arcus a écrit :
>>> I know SBo and Slackware doesn't have a system in place to track
>>> dependencies - and most of the time that suits me just fine. However,
>>> on occasion, I stumble over a piece of SBo software installed on my
>>> machine - such as a library, and I would like to know why is it there
>>> - which package needs it. I was thinking that, if when using the
>>> search field on SBo website, it would also search through the .info
>>> and README files of packages, I could easily get a list of packages
>>> which depend on or use the library - and spot if one of them is
>>> something that I use or have installed. It would be crude, but I think
>>>   it would work.
>> Why bother? Just leave this package alone, or if you are really curious,
>> remove it and see what happens.
> Hmm - I'm not sure that is a very useful piece of advice in practice.> You would have to test all the functionality of every single piece of
> software installed, to find out what is affected.

That's why if you are not sure why and when it was installed,
me actual advice is to just keep it.

More information about the SlackBuilds-users mailing list