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