On Mon, Jul 20, 2009 at 3:12 PM, Jack Johnson<knapj...@gmail.com> wrote:
>
> On Mon, Jul 20, 2009 at 9:27 AM, Nigel Kersten<nig...@google.com> wrote:
>> If you never use Puppet with Mac clients, you can stop reading now.
>
> More of a lurker than a user, but I'll comment anyway.
>
>> I believe the default should be the pkgdmg provider, which takes a
>> http:// url for a pkg inside a dmg.
>
> I agree, but lately I have stumbled across a couple vendor DMGs that
> have multiple packages inside, and at least one has both the install
> and uninstall PKGs.
>
> So, not knowing what the default handling is, multiple PKGs in one DMG
> would be the *only* downside I can see to changing the default
> provider on OS X, and at least short-term if it's not already handled
> it could be "fixed" with a documentation note.

The pkgdmg provider does currently install all pkgs it finds in the dmg.

                    mounts.each do |mountpoint|
                        Dir.entries(mountpoint).select { |f|
                            f =~ /\.m{0,1}pkg$/i
                        }.each do |pkg|
                            installpkg("#{mountpoint}/#{pkg}", name, source)
                        end
                    end

I'd argue you should just repackage in a new dmg if you've got dmgs like that.

I just find the apple provider really clunky. You need to set up your
own relationships to download the compressed pkg from somewhere and
put it on the local filesystem, then install the package, leaving the
package lying around.




>
> -Jack
>
> >
>



-- 
Nigel Kersten
nig...@google.com
System Administrator
Google, Inc.

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to