On Thu, 21 Apr 2022 09:09:16 -0400, Michael Orlitzky wrote: > It's getting harder and harder. There's always GCC, which is going to > take you most of the day to build and will probably require -j1 to keep > you from running out of memory. But aside from that, the big ones are > > * dev-lang/rust: pulled in by anything that needs SVG support unless > you unmask an old insecure version of librsvg or can tolerate half- > broken SVG support. This takes over 24h, requires -j1, and gets > worse every day because it bundles all of its (growing list of) > dependencies. > > * LLVM: needed by rust, some video cards, and certain picky packages. > This one is at least _legitimately_ large but has annoying point > releases every once in a while that trigger a rebuild for little > benefit. Again, expect ~24h. > > * net-libs/webkit-gtk: if you're avoiding firefox (which is huge, > and requires rust, which is huge), then this is your best bet for > a browser engine. Even if you don't use it directly, other apps > like evolution (mail client) can pull it in. It too is huge, just > not as bad as the others. This one finishes in something like 18h > for me.
Firefox and Rust have -bin packages - not so lucky with LLVM and webkit-gtk. -- Neil Bothwick Heisenberg's Uncertainty Principle: The location of all objects cannot be known simultaneously. Corollary: If a lost thing is found, something else will disappear.
pgp3w6Eaj3QoX.pgp
Description: OpenPGP digital signature