Hi All, I'm successfully using pkg_deploy to deploy DMG-encapsulated packages on Mac Clients. My question would be - since Puppet is essentially used to define a "state" that the computer is in, what would be the best way to maintain a "state" after deploying a package?
For example, if you deployed a package to install Microsoft Office, you would probably ensure that the Microsoft Office directory (as well as the individual .Apps) was Present. If the directory WASN'T present (someone deleted it, for example), is there a way to call pkg_deploy again to re-deploy the package, or would you have to keep the Microsoft Office directory structure on the Puppetmaster server (inside your module/files directory, for example) in order for it to send the directory structure down to the damaged client? In that vein (and a separate question), how does puppet know that pkg_deploy has been run and that the DMG-encapsulated package has been run/installed? It doesn't call pkg_deploy on subsequent catalog checks by the client - so it's not bringing down the DMG again and attempting an install. Is there some sort of "receipt" that it checks - or does it actually USE the Receipts directory to monitor installation? I know I'm trying to use Puppet to maintain staff and lab computers - which is somewhat unconventional, but it stands up to the implementation! Thanks for all your help and support! -Gary --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
