• F04118F
    link
    fedilink
    arrow-up
    13
    arrow-down
    1
    ·
    4 months ago

    Is compiling it yourself with the time and effort that it costs worth more than a few GB of disk space?

    Then your disk is very expensive and your labor very cheap.

    • cley_faye@lemmy.world
      link
      fedilink
      arrow-up
      12
      arrow-down
      1
      ·
      4 months ago

      For a lot of project “compiling yourself”, while obviously more involved than running some magic install command, is really not that tedious. Good projects have decent documentation in that regard and usually streamline everything down to a few things to configure and be done with it.

      What’s aggravating is projects that explicitly go out of their way to make building them difficult, removing existing documentation and helper tools and replacing them with “use whatever we decided to use”. I hate these.

    • BeigeAgenda@lemmy.ca
      link
      fedilink
      arrow-up
      8
      ·
      4 months ago

      I should have noted that I’ll compile myself when we are talking about something that should run as a service on a server.

    • recarsion@discuss.tchncs.de
      link
      fedilink
      arrow-up
      3
      ·
      4 months ago

      99% of the time it’s just “make && sudo make install” or something like that. Anything bigger or more complicated typically has a native package anyway.

    • ReveredOxygen@sh.itjust.works
      link
      fedilink
      English
      arrow-up
      5
      arrow-down
      4
      ·
      edit-2
      4 months ago

      They didn’t say anything about compiling it themselves, just that they prefer native packages to flatpak

      edit: I can’t read

      • Batbro@sh.itjust.works
        link
        fedilink
        arrow-up
        9
        ·
        4 months ago

        2 comments up they said

        If the choice then is flatpack vs compile your own, I think I’ll generally compile it, but it depends on the circumstances.