PKGSRC at The University of Wisconsin–Milwaukee. reddit / BSD ---------------------------------------------------------------------- liveoneggs · 2017-05-17 21:07 very nice. Agreed on all counts. ---------------------------------------------------------------------- teksimian · 2017-05-18 03:50 Looking forward to trying it out. Coming from freebsd ports. ---------------------------------------------------------------------- sigzero · 2017-05-18 20:41 That's pretty interesting. ---------------------------------------------------------------------- josuahdemangeon · 2017-05-20 08:35 On the other hand, when a software is really well-made, the "caveman" installing goes just fine. There seems to be a scale of built quality (making the source compile/install without issue): 1. languages 2. libraries 3. programs without libraries 4. programs with libraries Probably due to the fact that if a programming language (often in C) can not compile, nothing else can be built on top of it, so many efforts are done to get it built everywhere (often C89 source base like [lua](http://www.lua.org/source/5.3/luaconf.h.html#LUA_USE_C89) or [python](https://www.python.org/dev/peps/pep-0007/#c-dialect)). The same occurs for libraries, but less software is written ontop of a library than ontop of a language, so a little bit less constraint. Then the programs: if they break, one program does not work, end of the story. These are less often dependencies for building other programs (but for make, coreutils...) and do not have an as high pressure from the community. I see less efforts to get them built properly than for libraries and programming languages. Some programs have a lot of dependencies, and it gets the job harder as you have to deal with location of the libraries, the various configuration options... If no library is used, no configuration is required (is *truely* portable), does not use nonstandard extensions, then "caveman" install goes pretty well. If the package is not "self contained", you need to be lucky with the system you are running: location of libraries: [`/usr/X11R6/include`](http://www.tldp.org/LDP/Linux-Filesystem- Hierarchy/html/usr.html) instead of `/include` or at least `/usr/include` or `/usr/local/include`, in a compatible version... ---------------------------------------------------------------------- josuahdemangeon · 2017-05-20 08:38 This is not a better-to worst list: to deal with X11, you *do need* X11 libraries. To deal with JPEG or XML, you may not want to implement you own parsers in every program. Sometimes the maintainer is not supporting the project, and forking it would be too much work, so the packages are fixed at packaging time rather than at development time, and the package work, but nothing is submitted upstream. "caveman" installs are often pain in the ass, but they lead to systems with only packages that build without pain (those gets avoided). I prefer this rather than having a package manager installing broken software that work because they have been fixed. ---------------------------------------------------------------------- josuahdemangeon · 2017-05-20 08:46 That being said, you can have a only self-contained, `-Wall -Wpedantic -Wextra` packages that use very few libraries ontop of a very well- designed operating system, and still have a lot of work! That is precisely where I agree with the article. :)