On Saturday, May 5, 2012 1:40:36 PM UTC-7, Luke Kanies wrote: > > > First, is there a reason not to just maintain this as a module on the > forge? > > We're trying to keep the builtin types to the minimum that most people > will use, and are even doing things like moving the Nagios types to a > module, rather than shipping them in core. >
sounds fine to me.. once I learn how to do that :) > > Regardless, though, I agree the name is important. Most people would > agree I'm not the best person to give advice on names, but I'd go with > something like svcproperties. > it does seem to have potential overlap with windows registry types, though. So while "sysproperties" could work with that, "svcproperties" would not, seems to me. If it makes sense to have this class shared between those two uses. I dunno. Any ms-windows developers reading this? > -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-dev/-/XlCwK5l5RsgJ. 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.
