3 ms·
But why would it need all of those dependencies?
by IshKebab 2y ago
But why would it need all of those dependencies?
- groby_b 2y agoBecause all dependency managers at some point devolve to "install ocean, then boil ocean". (If you care, "brew deps <package> --tree" will tell you.)
- yu3zhou4 2y agobrew deps eza --tree prints: eza └── libgit2 ├── libssh2 │ └── openssl@3 │ └── ca-certificates └── openssl@3 └── ca-certificates
- deleted 2y ago[deleted]
- jasonpeacock 2y agoBecause most of those are dependencies required to build the actual dependencies. There's (generally) 4 types of dependencies: - Toolchains (frameworks, compilers) - Build (headers and libraries) - Runtime (libraries) - Test (frameworks, headers, libraries) And those dependencies all bring their own dependencies...
- Aaron2222 2y agoFrom what I can tell, it doesn't: $ brew deps --include-build eza autoconf automake ca-certificates cabal-install certifi cmake ghc ghc@9.8 libgit2 libssh2 llvm@18 lz4 m4 mpdecimal ninja openssl@3 pandoc pkg-config python@3.11 python@3.12 readline rust sphinx-doc sqlite xz zstd