Issue #2479 has been updated by Nigel Kersten.
So while I agree with the sentiment, I'm not so sure I think this kind of naming schemea is the best solution. It definitely feels like puppet and puppetd both don't need to exist, but it kind of bugs me how similar the following commands could end up being: <pre> puppet --server foobar puppet server </pre> ---------------------------------------- Feature #2479: All functionality should be available from a single executable http://projects.reductivelabs.com/issues/2479 Author: Luke Kanies Status: Accepted Priority: Normal Assigned to: Category: executables Target version: 0.26.0 Complexity: Unknown Affected version: 0.24.8 Keywords: We currently have 9 executables, and their interfaces are understandably diverged. We should copy the git folks and switch to a single executable ('puppet', of course), and then make each existing kind of functionality available via that executable. I see the following areas: <pre> puppet ca # puppetca puppet resource # ralsh puppet server # puppetmasterd puppet bucket # filebucket puppet doc # puppetdoc and pi, i think puppet agent # puppetd puppet queue # puppetqd puppet trigger # puppetrun </pre> -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://reductivelabs.com/redmine/my/account --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Bugs" 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-bugs?hl=en -~----------~----~----~----~------~----~------~--~---
