ryandesign at macports.org
Tue Jan 15 00:29:57 UTC 2019
On Jan 14, 2019, at 03:33, René J.V. Bertin wrote:
> 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 [https://github.com/RJVB/macstrop/blob/master/macports/bin/] 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)?
I am not aware of anything like this existing for MacPorts.
More information about the macports-dev