Acceptable-Formulae: update static library guidance.

Resulting from discussion in https://github.com/Homebrew/homebrew-core/pull/162352
This commit is contained in:
Mike McQuaid 2024-02-14 08:50:24 +00:00
parent eb9ac8d3e5
commit bb57a09be0
No known key found for this signature in database
GPG Key ID: 3338A31AFDB1D829

View File

@ -73,11 +73,11 @@ Clang is the default C/C++ compiler on macOS (and has been for a long time). Sof
We're a package manager so we want to do things like resolve dependencies and set up applications for our users. If things require too much manual intervention then they aren't useful in a package manager. We're a package manager so we want to do things like resolve dependencies and set up applications for our users. If things require too much manual intervention then they aren't useful in a package manager.
### Static libraries ### Shared vs. static libraries
In general, formulae should not ship static libraries since these cannot be updated without a rebuild of the dependant software. In general, if formulae have to ship either shared or static libraries: they should ship shared ones.
If a formula gets a lot of requests to install static libraries, they may be installed by the formula. If they can ship both, they should.
Applications in homebrew/core linking against libraries should link against shared libraries not static versions. Shipping only static libraries should be avoided when possible, particularly when the formulae is depended on by other formulae since these dependents cannot be updated without a rebuild.
### Stuff that requires vendored versions of Homebrew formulae ### Stuff that requires vendored versions of Homebrew formulae