dependencies.
The behaviors involved are pretty straightforward, but you can't
make big assumptions about what dependency cycles mean based on your
experience in other systems.
Cheers,
Mike Lococo
--
You received this message because you are subscribed to the Google Groups Puppet
Users group
.
Cheers,
Mike Lococo
On 08/25/2011 06:29 PM, R P Herrold wrote:
On Thu, 25 Aug 2011, Mike Lococo wrote:
2) You must understand how the yum and rpm os commands work, and
specifically how they each handle dependencies and circular deps
(yum works to satisfy deps, rpm fails unless all deps
that there's been a patch sitting
unmerged for almost two years.
Folks who work around this issue do so with execs, but I think more
often people just give up and let unneeded packages build up like cruft.
Cheers,
Mike Lococo
--
You received this message because you are subscribed to the Google
. The
last option is likely to be the least time-consuming IMO. If you want
details on my packaging setup, feel free to reach out to me offline.
Cheers,
Mike Lococo
--
You received this message because you are subscribed to the Google Groups Puppet
Users group.
To post to this group, send email
On 01/18/2011 03:06 PM, Avi Miller wrote:
Mike Lococo wrote:
2) Use the yum-driven options *AND* run your own satellite server so you
can ping it as often as you like.
You don't need a Satellite Server for this, just a plain Yum server will
do, which is essentially just httpd + createrepo
performance of puppet-runs, and has no
downside that has been discussed in its bug.
Cheers,
Mike Lococo
--
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
