Because I have finer control of the deployment targets and compile options anf such. Back when our CI used homebrew and all canned binaries, it wasn’t uncommon for a build to finish sucessfully but then crashing at runtime because of broken references to OS symbols and such. The final straw that made me yeet them entirely was when I realized some library (might have been opencv or fftw-3 maybe) depended by default on openblas instead of accelerate, and openblas was linked against libstdc++ 🙃
Gregorio Litenstein Goldzweig Médico Cirujano • Fono: +56 9 96343643 • E-Mail: [email protected] On 29 Sep 2025 at 21:04 -0300, Ryan Carsten Schmidt <[email protected]>, wrote: > On Sep 29, 2025, at 16:11, Gregorio Litenstein wrote: > > > Would it be possible to add some manner of configuration option (or > > possibly extra command-line switches) so that the -s and -b command-line > > switches aren't taken into account for packages (and their dependencies) > > that only got pulled-in as the result of a `depends_build`? > > > > I have a similar desire which is for there to be a way to tell a port to > build from source while allowing its dependencies (of any type, not just > build dependencies) to be installed or upgraded from binaries. > > > > My use case is the following: I'm building a large program that depends on > > things like ffmpeg, librsvg (and thus rust), among others, and I want it to > > be truly redistributable, so I want to build at least all direct > > dependencies myself. > > > > How does building it yourself make it redistributable? > > >
