View Single Post
  #5   (View Single Post)  
Old 12th April 2010
Broodjegehaktmetmayo Broodjegehaktmetmayo is offline
Shell Scout
 
Join Date: Sep 2008
Posts: 92
Default

Quote:
Originally Posted by TerryP View Post
Except for what you must actually compile and run the program for, many things can be found out by inspecting the files. For example the Makefile will tell you configuration data available (think make config and old knobs), pkg-plist and or Makefile the things contents (names of programs, manuals, paths, etc), and so on.


If you look at the dependencies declared in the Makefile you'll have an idea of what needs to be installed; special make targets can even give a more detailed list. Take a look at the ports manual page and the big kahunua in Mk for details.


How long crap actually takes to compile on your hardware, you kind of get a feel for after a while. For example, I know Firefox takes a good 2 1/2-3 hours to build on my laptop. Plus any dependencies.
I like how you all just push me into deep waters, but as a complete noob for me it is quite an accomplishment having been able to install FreeBSD, KDE, sound, printer, flash, and so on and so forth, and even doing that without ruining my XP (dual boot). In order for me to understand the Makefile and all that is related will require more knowledge than I currently have as a noob. it takes time, but my goal is to ultimately be able to give you all answers to questions you all can't solve. We'll get there (in about 10 years ).

Thanks again
Reply With Quote