Juan, I am confused. These so-called "options" are undocumented but should not be used by any user because their semantics could change any time. For example, xcodeversion only means how to handle xcode related tools and the most frequent value ("2.1"), as Kevin notes it, only means 2.1 or higher, but once we encounter an incompatible version of xcode, we will need to add a new value and update the semantics. We certainly do not want users to override this setting by putting whatever they think this would mean, this "option" is set by MacPorts infrastructure and it's better to keep users away from it. All that, including portverbose, porttrace, etc. were never intended to be options users could configure, they are just a way to express some information through the whole program. In fact, I do not understand why you found those in your ports.conf file. Mine is based from MP's ports.conf.in which does not mention those "options": http://svn.macosforge.org/projects/macports/browser/trunk/base/doc/ ports.conf.in That's why I am just confused when I read that you want to document that in ports.conf.5. Paul On Feb 20, 2007, at 07:14, Kevin Ballard wrote:
On Feb 19, 2007, at 3:31 PM, Juan Manuel Palacios wrote:
Hello guys! I'm going over some more documentation in my quest to advance on the 1.4 release, and I have some question for you guys about some undocumented options in the porsts.conf file. What exactly do the following do?
-) porttrace: sets trace mode on by default, no need to pass -t?
That appears to be the case, though I'm not going to spend the time making 100% sure
-) portverbose: kinda self explanatory, but I wasn't able to figure out what verbosity level is enabled, -v or -d?
-v
-) xcodeversion & xcodebuildcmd: Xcode related block in base/src/ darwinports1.0/darwinports.tcl is rather involved, so I wasn't able to gather much information on these....
That block detects the current version of xcode and sets those variables. xcodeversion has several possible settings, but the important bit is that Xcode of version 2.1 or later will have "2.1" be the value of that variable (according to the comments, no need was seen to know if it's later than 2.1).
xcodebuildcmd gets set to the proper command to use in order to build an Xcode project from the command-line - basically this is intended for systems with pbxbuild instead of xcodebuild.
-- Kevin Ballard http://kevin.sb.org eridius@macports.org http://www.tildesoft.com