New /bin/sh based script to manage ports

[Doug Barton]

David J. Weller-Fahy wrote:

> One thing I did notice is that you use only the pkgdeps from the
> +CONTENTS files to determine dependencies.  Is there a particular reason
> (besides speed) that you went with the pkgdeps instead of the *DEPENDS
> variables in the port? I noticed (for the mailfront port, in
> particular) that bglibs was not listed as a dependency by portmaster,
> but is a build dependency of mailfront, and wondered what implications
> that could have.

This depends on which direction you're approaching the problem from. When
building a port, the check for whether the dependencies of the port are up
to date uses the list from 'make all-depends-list', which will include build
dependencies. However, once a port has been built and installed
successfully, the list of ports which have a dependency on the updated port
is cross checked between the +REQUIRED_BY in the package directory and the
+CONTENTS files of the other installed ports. In this way we can be sure
that all appropriate dependencies are recorded, and updated. Since
BUILD_DEPENDS are not registered in the +CONTENTS or +REQUIRED_BY files,
they don't show up at that stage, and portmaster doesn't update information
about them (because that information doesn't exist).


hth,

Doug

-- 

    This .signature sanitized for your protection