Oversimplifying things quite a bit, the BSD ports system provides a directory-tree
of already-ported software. Once you've set up the ports system, you just cd
to the named package in the ports tree , type bsdmake and (hopefully) your machine
goes out, FTPs the source code for the package, examines it for any library
dependencies (and installs those libs if possible), and builds the package for you.
It makes something like RPM look like the hack it really is.
As more packages get tweaked for Darwin, this will mean that thousands of
timetested BSD apps will be only keystrokes away.
Ok, can someone give a quick list of these BSD apps? (ie. what I am missing by not doing this, what will I gain by it?)
Are these BSD specific apps, or just an efficient way of installing apps that have already been ported to BSD?
ie. I haven't checked (it may already be there), but I plan to install procmail and elm. I'm having trouble with elm not finding C libs (then again, maybe I need to make a link to Libraries from /lib). If I install this BSD ports pkg, could I then more easily just grab a BSD port of elm and it would install, vs. grabbing it myself, running Configure, and then make?
Again, maybe this is like trying to describe the smell of an orange to someone that has never smelled one (ie. can't be done). Just trying to get a feel for what this is. Sounds potentially useful.