Containers are a workaround and an overkill solution to this problem. It's a pain in the ass when you need to enter a "blessed" environment to build your proje

Containers are a workaround and an overkill solution to this problem. It's a pain in the ass when you need to enter a "blessed" environment to build your project. By "blessed", I mean a container environment, a chroot or just some environment variables that need to be set. > dnf pkgcontainer-run ~/dev/myproject make The issue with this kind of builds is that they integrate poorly with your $EDITOR (or IDE). When I run a build, I want the results to be piped back to my editor so I can comfortably jump to the files with errors and warnings in them. And it's not only the build, it's also running your application, running the debugger, static analysis, linters, etc. Requiring a special environment will introduce friction to all of these. Additionally, your suggestion of using "dnf" would require every developer in the project to use an OS where "dnf" runs. Builds should be reproducible as much as possible without depending on the OS. Development package managers solve lots of these problems, although having a package manager for every language is an issue.