Programming

17350 readers

269 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Follow the programming.dev instance rules
Keep content related to programming in some way
If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities [email protected]

founded 1 year ago

MODERATORS

[email protected]

Why I Left NixOS for Ubuntu (fd93.me)

submitted 6 months ago by [email protected] to c/[email protected]

46 comments fedilink hide all child comments

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.

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 25 points 6 months ago (3 children)

Since I bricked my Debian setup in an unfortunate accident involving compiling from source

How on earth?

[–] [email protected] 16 points 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.

[–] [email protected] 9 points 6 months ago* (last edited 6 months ago) (2 children)

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

I really like Pantheon Files.

[–] [email protected] 2 points 6 months ago

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

[–] [email protected] 2 points 6 months ago* (last edited 6 months ago) (1 children)

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.

[–] [email protected] 4 points 6 months ago* (last edited 6 months ago) (1 children)

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.

[–] [email protected] 8 points 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.

[–] [email protected] 0 points 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.