• Trigg@lemmy.world
    75·
    8 months ago

    Man updating packages by compiling them is so stupid

    Oh look 15 updated packages from AUR

    • funkajunk@lemm.eeEnglish
      27·
      8 months ago

      I always go with the binary version if it’s available in the AUR, ain’t nobody got time for that.

    • BCsven@lemmy.ca
      9·
      8 months ago

      I mean yes if time is an issue, but compiled code on your own hardware is specifically tuned to your machine, some people want that tiny tweak of performance and stability.

        • BCsven@lemmy.ca
          1·
          8 months ago

          But compiled on some other machine. Compiling on your own hardware optimizes it for that specific hardware and what that chip supports etc.

            • BCsven@lemmy.ca
              1·
              8 months ago

              Ah, thought you meant in the AUR. I’m used to OBS where you have binaries and source available (OBS meaning OpenBuildService, not the screen recorder)

      • zueski@lemm.ee
        3·
        8 months ago

        I use both for different purposes. Gentoo’s feature flags are the reason I wait for compiles, but only for computers a touch the keyboard with. Everything else gets Arch.

      • adONis@lemmy.world
        1·
        8 months ago

        would you mind elaborating on the benefits? like what does one actually gain in a real-world scenario by having the software tuned to a specific machine?

        disk space aside, given the sheer amount of packages that come with a distro, are we talking about 30% less CPU and RAM usage (give or take), or is it more like squeezing out the last 5% of possible optimization?

        • BCsven@lemmy.ca
          4·
          8 months ago

          Closer to thr 5% . Between the intermediate code and final code writing there is an optimization stage. The compiler can reduce redundant code and adjust based on machine. i.e. my understanding is an old 4700 can have different instruction sets available than the latest intel.gen chip features. Rather than compile for generic x86 the optimization phase can tailor to the machine’s hardware. The benefits are like car tuning, at some point you only get marginal gains. But if squeezing out every drop of performance and reducing bytes is your thing then the wasted compiling time may not been seen as waste.

  • msage@programming.dev
    24·
    8 months ago

    Special Fuck You to:

    • clang
    • LibreOffice
    • Firefox
    • llvm

    I only use dwm, so no idea how long it takes to compile KDE or Gentoo Gnome.

    Everything else is so quick. Just those four take 20-30 minutes each.

    • porl@lemmy.worldEnglish
      24·
      8 months ago

      Before I had a proper internet connection (had to ask permission to borrow a dial up account) I bought a magazine that had a picture of a cow on it saying that Larry the cow was different. It was a DVD image of the stage one mirror of this new fangled Gentoo thing.

      Learnt from the magazine how to install a bootloader and so on and then “bravely” typed emerge world into the terminal after configuring the list of all the packages I wanted. Including a full desktop (KDE I think but may have been Gnome). And Firefox. And Open Office. And some multimedia stuff I don’t remember.

      On a Pentium ii.

      Took a week before I could do the next step :D

  • Pacmanlives@lemmy.world
    10·
    8 months ago

    I am rolling a few Gentoo VM’s these days and it’s really not that bad to compile things these days and I am on an old ass (10 year) dual Xeon setup. I remember X taking a few days to a week to compile back in the 2000’s

  • adONis@lemmy.world
    4·
    8 months ago

    Oh man, just today I was messing around with flatpak, where I tried building webkit2, which took ages, or almost an hour (to be more specific).

    And I was thinking to myself if that’s what Gentoo feels like.

  • cygon@lemmy.world
    2·
    8 months ago

    I usually compile with --quiet-build=y, it doesn’t have to be configures and makefiles blasting into a shell window the whole time. On the rare occasions where a build fails there’s still the log in /var/tmp/portage/....