I've made a first pass at trying to include some of the darwinbuild related metadata in the xar archives created by packageRoots. Basically, I've added a darwinxref module that just takes the project information that is in the plist from the database and exports it in either plist or xml style like exportIndex does. Then packageRoots calls this, exports the information in xml format, and has xar add it as a subdoc in the archive named 'darwinbuild'. Rob
Great Rob! I'll take a look at this and commit it ASAP, probably tomorrow (Sunday). Shantonu On Sep 30, 2005, at 10:39 AM, Rob Braun wrote:
I've made a first pass at trying to include some of the darwinbuild related metadata in the xar archives created by packageRoots. Basically, I've added a darwinxref module that just takes the project information that is in the plist from the database and exports it in either plist or xml style like exportIndex does. Then packageRoots calls this, exports the information in xml format, and has xar add it as a subdoc in the archive named 'darwinbuild'.
Rob
_______________________________________________ darwinbuild mailing list darwinbuild@opendarwin.org http://www.opendarwin.org/mailman/listinfo/darwinbuild
This is neat! I've committed it, and tried it out a bit. The packageRoots stuff works fine, however exportProject seems to have some issues with inheritance. For example: G5:/Volumes/Darwin/Build root# darwinxref version xnu xnu-792.2.4 G5:/Volumes/Darwin/Build root# darwinxref exportProject xnu | grep version version = 792 So it picked up the 8A428 plist definition, even though we probably want an effective "merge" of all the builds that contributed (or overrode) useful properties. I'll look at this a bit more later. Shantonu On Oct 1, 2005, at 7:55 PM, Shantonu Sen wrote:
Great Rob!
I'll take a look at this and commit it ASAP, probably tomorrow (Sunday).
Shantonu
On Sep 30, 2005, at 10:39 AM, Rob Braun wrote:
I've made a first pass at trying to include some of the darwinbuild related metadata in the xar archives created by packageRoots. Basically, I've added a darwinxref module that just takes the project information that is in the plist from the database and exports it in either plist or xml style like exportIndex does. Then packageRoots calls this, exports the information in xml format, and has xar add it as a subdoc in the archive named 'darwinbuild'.
Rob
_______________________________________________ darwinbuild mailing list darwinbuild@opendarwin.org http://www.opendarwin.org/mailman/listinfo/darwinbuild
_______________________________________________ darwinbuild mailing list darwinbuild@opendarwin.org http://www.opendarwin.org/mailman/listinfo/darwinbuild
participants (2)
-
Rob Braun
-
Shantonu Sen