On 01/05/2011 09:39 PM, John Warburton wrote: > On 6 January 2011 12:52, Nigel Kersten <ni...@puppetlabs.com > <mailto:ni...@puppetlabs.com>> wrote: > > > > On Wed, Jan 5, 2011 at 2:52 PM, Michael Knox <michael.knox.au > <http://michael.knox.au>@gmail.com <http://gmail.com>> 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 > > John
At least in RPM-land, packages can be built as non-root (and is highly recommended you do so). You're right that packages can't be installed w/o root, but they can be relocated if you build your package right. If you're installing the package w/ puppet root privs are already there. -Doug
signature.asc
Description: OpenPGP digital signature
