Issue #2740 has been updated by Nigel Kersten.

Ben Hearsum wrote:
> I think that a) makes the most sense, but b) isn't awful either. If this 
> behaviour is sometimes desirable it could be controlled with a flag, too.

Yeah. I'm thinking of environments where you're installing from NFS but 
connectivity may be spotty enough to cause problems with large packages that 
take a long time to install.

Given the approach of only providing bug fixes (and I most certainly consider 
this a bug) in 0.25.x releases, how about I simply patch it to not trash the 
dmg if it's a filesystem path, and if someone decides they need something like 
"cache => true" in the provider, I'll do it if someone requests it.

This is trivial. I'll have time to get to it in the next few days.
----------------------------------------
Bug #2740: pkgdmg provider should not be deleting package files
http://projects.reductivelabs.com/issues/2740

Author: Ben Hearsum
Status: Accepted
Priority: Normal
Assigned to: Nigel Kersten
Category: package
Target version: 
Affected version: 0.24.8
Keywords: 
Branch: 


Currently, the only good way to install packages through the pkgdmg provider is 
to run an HTTP service. For our setup, this is far from ideal. We keep an NFS 
mount on all our managed machines, and serve files through that.

In my opinion, the pkgdmg provider should never be deleting files. At the very 
least, it should be optional behaviour.


-- 
You have received this notification because you have either subscribed to it, 
or are involved in it.
To change your notification preferences, please click here: 
http://reductivelabs.com/redmine/my/account

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Puppet Bugs" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/puppet-bugs?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to