<span class="Apple-style-span" style="font-family: verdana, sans-serif;">Hi Todd</span><div><span class="Apple-style-span" style="font-family: verdana, sans-serif;"><br></span></div><div><span class="Apple-style-span" style="font-family: verdana, sans-serif;">I'm happy to go with the majority vote on whether puppetd and/or puppetmasterd should move to sbin.</span></div>
<div><span class="Apple-style-span" style="font-family: verdana, sans-serif;"><br></span></div><div><span class="Apple-style-span" style="font-family: verdana, sans-serif;">In the case of the Solaris packages I maintain, these have to go under /opt/csw as I'm using the csw distribution mechanism. Similar rules will no doubt apply to other platform's porting systems, so fully consistent installs won't be possible unless we all jump ship to /opt/reductivelabs or similar. Nonetheless I think we should strive to be as consistent as possible.</span></div>
<div><span class="Apple-style-span" style="font-family: verdana, sans-serif;"><br></span></div><div><span class="Apple-style-span" style="font-family: verdana;">On the subject of consistency:</span></div><div><span class="Apple-style-span" style="font-family: verdana;">Some packages are a full puppet bundle (eg Solaris); others are separate puppetd and puppetmasterd (eg Debian)</span></div>
<div><span class="Apple-style-span" style="font-family: verdana;">Some autostart all daemons (eg Debian), some start puppetd only (eg Solaris), some don't start anything (eg Red Hat).</span></div><div><span class="Apple-style-span" style="font-family: verdana; ">Distros/porting systems may have 'rules' about the above which are fundamentally inconsistent, as is the case with install directories.</span><br>
</div><div><span class="Apple-style-span" style="font-family: verdana;"><br></span></div><div><span class="Apple-style-span" style="font-family: verdana, sans-serif;">Thanks for taking the initiative to contact us,</span></div>
<div><span class="Apple-style-span" style="font-family: verdana, sans-serif;"><br></span></div><div><span class="Apple-style-span" style="font-family: verdana, sans-serif;">Gary</span></div><div><br></div><div><br></div><div>
<div class="gmail_quote">2009/3/17 Todd Zullinger <span dir="ltr"><<a href="mailto:tmz@pobox.com">tmz@pobox.com</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Greetings puppet packagers,<br>
<br>
I'm Todd. I help maintain the puppet packages for Fedora and EPEL. I<br>
found your names and addresses associated with puppet packages for<br>
various Linux distributions and other operating systems. If I've<br>
included anyone mistakenly, please accept my apologies. Likewise, if<br>
there is a better address to reach the packagers of puppet for your<br>
distribution/OS, I'd be happy to learn about it.<br>
<br>
With that out of the way, the reason for this message is to seek your<br>
opinions and help in making puppet's installation process a slight bit<br>
easier for packagers and administrators.<br>
<br>
The initial question I have is about the location of the system<br>
binaries and scripts. Currently, the install.rb script in the puppet<br>
source release installs these in ruby's Config::CONFIG["bindir"]<br>
(typically /usr/bin on linux). On many distributions, we prefer to<br>
place the daemons and other administrator binaries and scripts into<br>
Config::CONFIG["sbindir"] (typically /usr/sbin).<br>
<br>
I submitted a patch¹ to install several of the binaries/scripts in<br>
sbindir by default (puppetca, puppetd, and puppetmasterd, and<br>
puppetrun). This matches what Debian does currently, I believe.<br>
Fedora is similar, though we are currently not installing puppetca in<br>
sbindir -- I think Debian is more consistent in that regard. ;)<br>
<br>
I think if we improve the puppet install script such that it is usable<br>
by more packagers, it might make all of our jobs just a bit easier.<br>
And if we choose sane defaults, we might even end up with less<br>
confusion for users who run multiple different operating systems.<br>
<br>
What are your thoughts on this? Feel free to reply to this message,<br>
or join the thread on the puppet-dev list. (The message-id, to keep<br>
things threaded, is: <a href="mailto:20090311073826.GP10507@inocybe.teonanacatl.org">20090311073826.GP10507@inocybe.teonanacatl.org</a>)<br>
<br>
Thanks for reading. And thanks for packaging puppet!<br>
<br>
¹ This is an incomplete patch, mainly to get comments from the<br>
community of users, developers, and packagers:<br>
<a href="http://groups.google.com/group/puppet-dev/browse_thread/thread/e63d8964dd508bbd" target="_blank">http://groups.google.com/group/puppet-dev/browse_thread/thread/e63d8964dd508bbd</a><br>
<font color="#888888"><br>
--<br>
Todd OpenPGP -> KeyID: 0xBEAF0CE3 | URL: <a href="http://www.pobox.com/~tmz/pgp" target="_blank">www.pobox.com/~tmz/pgp</a><br>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~<br>
Would you let the aliens land, please? They might be here to pick me<br>
up.<br>
-- Bill Hicks<br>
<br>
</font></blockquote></div><br><br clear="all"><br>-- <br>Gary Law<br>Email: <a href="mailto:garylaw@garylaw.net">garylaw@garylaw.net</a><br>Chat googletalk/messenger: <a href="mailto:gary.law@gmail.com">gary.law@gmail.com</a><br>
iChat/jabber/AIM: <a href="mailto:gary.law@mac.com">gary.law@mac.com</a><br>
</div>