depspec generator?

René J.V. Bertin rjvbertin at
Mon Jan 14 09:33:54 UTC 2019


I just realised why Debian packages only have a list of build dependencies in their specification: the dependencies of the generated packages are determined automatically from the dependencies of the shared libraries installed by each package.

I think MacPort "base" already has most of the code required to generate a depspec list from a new/upgraded port's destroot, as a means of verification and convenience for port maintainers. (A bit like my own port-check-conflicts.tcl [] which checks for activation conflicts).

Does something like this already exist, especially with an option to filter out indirect dependencies (= those already satisfied through dependency inheritance)?


More information about the macports-dev mailing list