On Sep 1, 2005, at 2:38 PM, Shantonu Sen wrote:
On Aug 31, 2005, at 4:43 PM, Kevin Van Vechten wrote:
I believe this would eliminate the most common cases for using the "-depsbuild" argument.
Yes, because you essentially end up putting all the inheritance tree on the command-line in the form of depsbuild arguments... In fact we should remove -depsbuild, since it's not clear where those builds would end up in priority after you've evaluated the inheritance chain based on the database.
Good point.
We may want to start putting darwinbuild compatibility versions in the plist, to indicate the minimum darwinbuild/darwinxref you need to import a plist. The sooner we do this, the easier a transition will be in the future (and the lesser support burden).
Good idea. Does "compat_vers" appeal to you? Monotonically increasing integer sound good? - Kevin