-
We use Linuxbrew on our systems at my workplace, mostly because we don't have root. Should I be worried about our IT upgrading system-level C libraries at some point? It appears that Linuxbrew compiled binaries have many system-level C lib dependencies. At first, it appeared that these were all from the glibc library which may have made dealing with IT system upgrades more manageable as I could have asked them to ignore glibc upgrades only. I then noticed I seem to recall Linuxbrew being less dependent on system-level stuff. Has this been changing gradually over time?
|
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 5 replies
-
It should just be glibc and system GCC (libstdc++ & libgcc_s). But both have retained ABI compatibility for a while so updating glibc and GCC should not be a concern. We enforce a minimum version but no maximum for this reason. If a situation arose where a future system glibc caused problems, then we could allow Homebrew's So you should be fine updating system libraries without it breaking anything. If anything does, then that's a bug. |
Beta Was this translation helpful? Give feedback.
It should just be glibc and system GCC (libstdc++ & libgcc_s).
libcrypt
(not to be confused withlibcrypto
) is a part of glibc.But both have retained ABI compatibility for a while so updating glibc and GCC should not be a concern. We enforce a minimum version but no maximum for this reason.
If a situation arose where a future system glibc caused problems, then we could allow Homebrew's
glibc
to be installed. The binaries we ship in our bottles are already set up so that they will prioritise Homebrew's glibc if installed. People who have a system glibc that's too old already rely on this feature.So you should be fine updating system libraries without it breaking anything. If anything doe…