Which isn't terrible, but you loose init scripts and the like.
Zach
On Tue, Nov 9, 2010 at 4:43 PM, bobics wrote:
> I get around this issue by installing Puppet as a gem.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To post to thi
I get around this issue by installing Puppet as a gem.
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@go
Hi Richard,
On Nov 6, 12:59 am, Richard Crowley wrote:
> You can't get around running an `apt-get update` but you can do that
> from an exec resource in an earlier run stage.
>
> stage { pre: before => Stage["main"] }
> exec { "apt-get update": stage => "pre" }
>
> You'll probably want to do your
Hi Patrick,
On Nov 6, 1:25 am, Patrick wrote:
> First, if you update puppet, it's probably a good idea to update facter.
I thought that would be done by dependencies? If not, yes that is also
what I need :)
> Second, are you trying to use lenny-backports for everything or just puppet
> and rela
