<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On 2. okt. 2009, at 18.34, Nigel Kersten wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><a href="http://www.debian-administration.org/users/dkg/weblog/53">http://www.debian-administration.org/users/dkg/weblog/53</a><div><br></div><div>andy passed this on to me this morning, and I thought he made some interesting points (talks about the puppet/puppetmaster packages specifically)</div>
</blockquote></div><br><div>Yes.</div><div><br></div><div>While I do not share his fears about puppetmaster doing self-puppetizing in its spare time, I do share his views on separation.</div><div><br></div><div>The fast, easy and possible wrong solution is to disable the puppet service by default in the puppet package.</div><div><br></div><div>A solution I favour is to create one package for the puppet service, one for the puppetmaster service, and one common package both depend on. This means we move a lot of things from the puppet package to a puppet-common package. That way we can make puppetmaster (and puppet) depend on puppet-common.</div><div><br></div><div><br></div></body></html>