On Wed, Jan 5, 2011 at 6:39 PM, John Warburton <[email protected]> wrote:
> On 6 January 2011 12:52, Nigel Kersten <[email protected]> wrote: > >> >> >> On Wed, Jan 5, 2011 at 2:52 PM, Michael Knox >> <[email protected]>wrote: >> >>> It would be neat if puppet could use tar.gz's as a source, instead of >>> just bare directory trees. So I've lodged a feature request: >>> https://projects.puppetlabs.com/issues/5786 >>> >>> Many of my manifests for applications need to cover the following >>> process: 1. Download .tar.gz to host >>> 2. Expand .tar.gz >>> 3. Whatever install process is required >>> >> >> I'm not totally against this, but I am curious why you haven't decided to >> build packages for these applications, as that should essentially contain >> all your desired functionality right? >> > > Our own situation is that we have developers who build their own > applications, and if we packaged them with RPM or pkg, then they would have > to be installed as root. We don't trust them enough for that, so right now > we run an exec as the application owner to unpack the tar.gz > > Do you just unpack once and leave it alone? Drop a marker file when an install script succeeds and you don't have to run it again? It sounds like we could maybe do a tar.{gz,bz2,zip} "package" provider, with simple install, uninstall, maybe the ability to specify versions by symlinks. -- You received this message because you are subscribed to the Google Groups "Puppet Users" 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-users?hl=en.
