Re: pkgsrc : dependencies : determination : how?

[Mayuresh Kathe <mayuresh%sdf.org@localhost>]

> From martin%duskware.de@localhost Tue Mar 29 12:56:41 2022
> From: Martin Husemann <martin%duskware.de@localhost>
> To: Mayuresh Kathe <mayuresh%sdf.org@localhost>
> Cc: netbsd-users%netbsd.org@localhost
> Subject: Re: pkgsrc : dependencies : determination : how?
>
> On Tue, Mar 29, 2022 at 12:45:35PM +0000, Mayuresh Kathe wrote:
> > the point i'm most concerned about is how pkgsrc manages to
> > figure out if a package has to be uninstalled or not, like
> > what if there are recursive dependencies shared amongst
> > multiple packages?
>
> That is very easy: on registering a package that depends on some other,
> the pkg adds itself to the +REQUIRED_BY list of the dependency.
>
> E.g. in my previous example xsane listed gimp as a dependency, and
> you can see this by:
>
>  > cat /usr/pkg/pkgdb/gimp-2.10.30/+REQUIRED_BY
> xsane-0.99.9nb19
>
> The more elegant way to query this (and a lot more) is via pkg_info
> (but I thought you would be asking about how it was implemented).
>
>
> Martin
>

yes, i was indeed very much leaning towards wanting to understand
how pkgsrc's package dependency management is implemented.
just an inane need to find out how things work on the inside.
apologies if i have been bothersome.
martin, again, thanks for responding. would appreciate more such
from you. and will definitely ask on that pkg list.
cheers.