Just to make things clear: We've worked out a plan of approach with David, with intermediate goals, etc. and he's working along that path. So while there are a lot of things we might have chosen to do instead (and may well subsequently do in addition) we don't want to complicate / side track this phase of things.
For those that missed the earlier discussion, the basic breakdown is: 1. Mechanical changes and differences supported by ruby. For example, literal "/" characters used to join file path components that need to be replaced with the File::Separator and similar. 2. Behavioral changes, such as threading / forking, which may function differently or not have analogs under MS Windows. In some cases this will require finessing (e.g. the system for shelling out & capturing the output) while in others it should be possible to simply construct MS Windows aware provider (e.g. User management). 3. Adding one or more MS Windows specific resource types. I'm thinking the registry is an obvious choice, and there may be others. After we get the first two finished we'll be able to say "it runs on windows" and it will make more sense to talk about further expansions. -- Markus -- 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.
