As createpackage has not been updated for quite some time, an alternative method of generating the package has been developed. It utilizes Apple's Developer Tools/GCC and a project called the Luggage, which in turn uses make to generate the package. It also can be dynamically fed new version numbers, for both Puppet and Facter. https://github.com/unixorn/luggage https://github.com/unixorn/luggage-examples/tree/master/puppet https://github.com/unixorn/luggage-examples/tree/master/facter
If you are deploying it using a patch management tool like Munki (munki.googlecode.com), it can use the proper protocol of querying the receipt db and therefore remove all the bits and pieces that were installed based upon their bill of materials. Allister Banks @sacrilicious On Nov 29, 3:53 am, Alexander Fortin <alexander.for...@gmail.com> wrote: > On 11/28/11 5:59 PM, Nigel Kersten wrote: > > > > > > > > > > > You should, yes. > > > I'd actually suggest the best thing to do is to run > > "conf/osx/createpackage.sh" to generate a proper Mac pkg out of the > > tarball. That will do some extra things like set up the right directory > > ownership for you. > > > The previous install.rb install should have put files into: > > > /usr/lib/ruby/site_ruby/1.8/puppet* > > /usr/bin/puppet* > > /usr/bin/filebucket > > /usr/bin/pi > > /usr/bin/ralsh > > /usr/sbin/puppet* > > and removing all those should effectively remove the install. > > Thanks Nigel, I've followed your suggestion and now I'm running puppet > v2.7.6 installed via gem > > PS I wasn't able to find the createpackage.sh script you suggested though > > -- > Alexander Fortinhttp://about.me/alexanderfortin/ -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
