If you've hung out in Linux enthusiast circles lately, you'll have heard whispers that Arch Linux is no longer hot product. Instead, all the cool kids are using something called NixOS. Since I bricked my Debian setup in an unfortunate accident involving compiling from source, I decided to give NixOS …

Hey all, thought this might be of interest to some here.

Wrote about why I moved from NixOS to Ubuntu after using it for several months on my daily driver. Suspect that this take is likely to be kind of controversial and court claims of skill issues, which might even be true.

Let me know what you think.

    • XTL@sopuli.xyz
      16·
      6 months ago

      I have actually done that once. Somehow managed to make install glibc over libc5 or something like that.

      That was a while ago, though.

    • fd93@programming.devOP
      123·
      6 months ago

      Debian really doesn’t like installing different versions of GUI libraries & their dependencies.

      I really like Pantheon Files.

      • Gamma@beehaw.orgEnglish
        2·
        6 months ago

        Pantheon Files is the best, i also compiled it from source when i was stuck on Pop!

      • Successful_Try543@feddit.de
        2·
        6 months ago

        I know, I’ve once messed around to install a newer QT framework which was required by some package I’ve downloaded directly. Did you install them from the repos or manually copied the files into place? At first I thought the issues were due to compiling source code, not installing conflicting libraries.

        • fd93@programming.devOP
          4·
          6 months ago

          I actually can’t remember as it would have been 6+ months ago now. The issue is probably fixed already by the Debian maintainers / Elementary Team / both.

          Likely something with Meson build / apt not playing nicely.

          • suy@programming.dev
            8·
            6 months ago

            I’ve been compiling apps depending on newer Qt and/or kdelibs versions for ages (back when the repository was literally called “kdelibs”, about 20 years ago).

            This has never been an issue for me. Even with autoconf/automake, I just compiled everything to its own prefix, so it doesn’t interfere with the system at all. You don’t even need to fix the build system in the cases where it’s broken/lacks features, if you leverage all the “path” variables (CPATH, LIBRARY_PATH, LD_LIBRARY_PATH, PKG_CONFIG_PATH, etc.). But autotools, cmake, qmake, and every build system I’ve used so far supports this out of the box.

            Not claiming it’s a skill issue, but I have to say I’m very surprised by reading any of this.

            Specifically, for Debian, I was told 20 years ago by a very wise person “you never do make install on Debian, specially not for the kernel”, and taught me how to use make-kpkg (or something like that, I don’t remember the name of the tool), which was a way to make a debian package of a self built kernel, which is obviously something that can’t be installed to its own prefix.

    • duhdugg@programming.dev
      11·
      6 months ago

      I also don’t understand. For compiling from source, why not use podman or docker to just compile everything into a tarball that can be extracted into /opt? I used to do this all the time when installing multiple php versions on a CentOS machine.