On Thu, Oct 1, 2009 at 3:57 PM, Luke Kanies <[email protected]> wrote: > So (Paul Lathrop will correct me if I'm wrong, I hope), it looks like > we decided on the following simplistic metadata for modules: > > * version > * name > * author > * source (i.e., a URL) > * requires
* license * platforms > The requires need to be able to specify either names or names and > version. I put version comparators in the "next version" bucket. So, for now, you should be able to specify "requires MODULE" or "requires MODULE version VERSION" but not "requires MODULE version greater than VERSION" > We also decided that the data will be stored in a file named something > like 'metadata.json', and the file format will be json. I'd say we settled on metadata.json, that json is what we will support at first, but clearly that leaves it open to support other formats later. > My plan at this point is to do the requires as either an array, or an > array of arrays: > > requires: foo, bar > requires: [foo, 1.0], [bar, 2.0] > > Comments? > > I'm partway to a first version, anyway. You are a machine! I was totally going to hack up a first pass at a tool this evening. Ah well, c'est la vie. --Paul --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/puppet-dev?hl=en -~----------~----~----~----~------~----~------~--~---
