First let me apologize for *not* submitting my patches upstream (and thanks, Christian, for merging them!). Given the appearance of "Puppet" throughout the library, I assumed that it had actually been forked, not vendored. Not that that's a great excuse for not submitting to the other fork. Anyway.
Anyway, I'm with Adrien and Mike: unvendor, make a dependency, and contribute to the upstream lib. Brian mentioned that plutil is slow and untenable. I'm with you 100% on "slow", but it works so I differ regarding "untenable". If it seems important that puppet continue to operate on OS X without the CFP library, then I think it's perfectly legitimate to include an API-compatible implementation in facter that just shells out to plutil. Finally, the monkey-patching of basic types freaks me out, since it's a global change. But hey, I'm a Pythonista by trade so maybe that's a personal problem. Dustin -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/puppet-dev. For more options, visit https://groups.google.com/groups/opt_out.
