On 02/27/2018 03:30 PM, Neil Bothwick wrote:
> 
> --with-bdeps=n. Once a package is installed, it doesn't matter what
> happens to its build deps.

FWIW, the rationale for enabling bdeps by default for "upgrade" actions
is that the old build deps are already installed; so if there's a major
security vulnerability in one of them, you probably want to update it.


Reply via email to