3 ms·

I cover both, but you're right about choice. Not looking to sway. I explained background, my position, and some reasoning. I'll try again. I don't compile the

I cover both, but you're right about choice. Not looking to sway. I explained background, my position, and some reasoning. I'll try again. I don't compile the whole OS, or as you say, spend dozens of hours compiling packages from source. In the small cases where I do compile something, it's this process: fedpkg clone -a -b ... packagename cd packagename # toy around, make customizations that justify the compilation fedpkg mockbuild dnf up ./results*/*/*.rpm You're making a strawman with this literal position of compiling everything, bathing it in hyperbole. I agree, that's a waste of time, so I don't run Gentoo. I run Fedora where I can compile what I need to. Reliably. Or I'd still be on Arch. I apply patches, test them, suggest fixes upstream. That's what I accomplish. I can't speak for everyone but I can try to help. You're welcome; it's literal maintenance. Again, not everyone does it. Remember when I said this? > While everyone may not do this, they absolutely benefit from the ability. Another reminder, this was the question: > what do you actually accomplish by compiling your OS? I do it [for components] so others don't have to. Christ. I'm explaining how it's used, not why you should change anything. I feel we mostly agree, I rambled - like I did here. It's rarely worth it. I found a decent middle ground. Build/test what I have to, most easily. Getting back on topic: more CPU cores help with the time this requires. Machine time is spent so human time isn't.

stouset 2y ago
Sorry, but I wasn’t making a straw man: the GP I responded to explicitly made the point that they wanted a manycore monster CPU to speed up compiling their entire OS from scratch. If all you’re talking about is compiling a few targeted packages for customization or performance reasons, that’s absolutely a reasonable and sensible approach to things. My question was targeted at the GP’s use case which I wholeheartedly believe is a largely senseless waste of time, effort, CPU cycles, and money.
- bravetraveler 2y ago
  > Sorry, but I wasn’t making a straw man: the GP I responded to explicitly made the point that they wanted a manycore monster CPU to speed up compiling their entire OS from scratch. This is what they said, emphasis mine: > **most** of my OS Want to try again? It's so arbitrary, I'm good. "49% would be acceptable, 51% - hah!". Nobody dare modify/test 'glibc' or any of the precious libraries. Later, test police :) No hard feelings, I'll admit I don't communicate well and like this stuff a little too much
  - stouset 2y ago
    Every continuum has arbitrary points, a la “when is a pile a heap”. In this case it becomes insensible somewhere between selecting a few packages which are genuine performance bottlenecks for your workloads or need specific compiler flags for necessary features, and spec’ing out hardware to fit a $5,000+ 192-core CPU so you can feel good about your kernel being able to take advantage of AVX512 for your Linux desktop box.

stouset 2y ago

Sorry, but I wasn’t making a straw man: the GP I responded to explicitly made the point that they wanted a manycore monster CPU to speed up compiling their entire OS from scratch. If all you’re talking about is compiling a few targeted packages for customization or performance reasons, that’s absolutely a reasonable and sensible approach to things. My question was targeted at the GP’s use case which I wholeheartedly believe is a largely senseless waste of time, effort, CPU cycles, and money.

bravetraveler 2y ago
> Sorry, but I wasn’t making a straw man: the GP I responded to explicitly made the point that they wanted a manycore monster CPU to speed up compiling their entire OS from scratch. This is what they said, emphasis mine: > **most** of my OS Want to try again? It's so arbitrary, I'm good. "49% would be acceptable, 51% - hah!". Nobody dare modify/test 'glibc' or any of the precious libraries. Later, test police :) No hard feelings, I'll admit I don't communicate well and like this stuff a little too much
- stouset 2y ago
  Every continuum has arbitrary points, a la “when is a pile a heap”. In this case it becomes insensible somewhere between selecting a few packages which are genuine performance bottlenecks for your workloads or need specific compiler flags for necessary features, and spec’ing out hardware to fit a $5,000+ 192-core CPU so you can feel good about your kernel being able to take advantage of AVX512 for your Linux desktop box.