RUN_DEPENDS and portmaster

[Matthias Fechner]

Dear Stefan,

Am 17.09.2018 um 14:31 schrieb Stefan Esser:
> But the behavior of portmaster will not be changed.
> RUN_DEPENDS are dependencies required to run a port, not dependencies
> required to install a port.
>
>
> And I do not care whether bsd.port.mk treats RUN_DEPENDS as if they
> were INSTALL_DEPENDS (which do not exist). The fact that bsd.port.mk
> works in that way is due to the fact, that it generally executes sub
> processes in a depth first manner. Portmaster distinguishes build and
> run dependencies and makes sure, that build dependencies not only exist,
> but are updated before the ports they depend on, while bsd.port.mk will
> use any build dependency that satisfies the range requirements (if any)
> and does not upgrade existing but outdated (in the sense that an upgrade
> is available) dependencies. Portmaster will then upgrade any out-dated
> run dependencies (again if an upgrade is available, not only if it is
> strictly required). Thus portmaster guarantees, that a port is built
> with the latest available build tools, and that run dependency upgrades
> see the upgraded port that requires them, in case they depend on it.

I fully understand you.

Maybe it will be a good idea to phase portmaster out as it seems to be a
unmaintable beast?

Maybe synth can replace it for users that are not used to poudriere?


Gruß
Matthias

-- 

"Programming today is a race between software engineers striving to
build bigger and better idiot-proof programs, and the universe trying to
produce bigger and better idiots. So far, the universe is winning." --
Rich Cook