That is really interesting, Linc. I just started using netbsd on a test box. I have only used pkgsrc binary packages for the programs that I have installed. I have not installed much with dependances, and all of the programs that I have installed is simply CLI programs. I had no idea that there were such problems. I could see how that would happen because the binary packages that are available for netbsd is very limited. So if you want to install anything interesting you need to install from source.Linc wrote: Well, the jist of it is that when using binary packages, it doesn't seem like the dependancies are checked at all, or if they are, there are plenty of missing packages, which breaks things. Also, you would think that if the binary package (or dependancy) was missing that somehow they would check and use the source package, and that doesn't happen either. Futher, to complicate things, there are several recent instances where I have used the source packages and had them not compile or had missing dependancies that couldn't be fulfilled. Not to mention, getting the source packages set up and working takes an hour to unpack the sourcetree after you get it.
I still think that pacman/apt-get is the answer.
I really hope that they get the package system worked out, because I want to install this on an alpha server and a test box that I can keep running and running without any issues. I really don't want dependancy issues, that is one reason why I haven't been working with Slackware a lot anymore.
The one thing that I don't like about netbsd is that when it installs a program, it does not tend to install all of the configuration files that are common. So you expect a program to work in a certain way, but it doesn't because the common config files that every Linux distro, including Slackware install for you. Bash and Vim are examples of this.
mowestusa

