On Thu, Oct 30, 2008 at 6:12 PM, Andrew Shafer <[EMAIL PROTECTED]>wrote:
> Arnau, Hi Andrew, > > The groupinstall is specific behavior to yum, it isn't an abstraction > supported by Package resource. Yep, *yum*: Support via yum. Required binaries: python, rpm, yum. Default for operatingsystem == fedoracentosredhat. Supported features: installable, uninstallable, upgradeable, versionable. SO, I imagine I should create a group_installable feature... is it? > If you really really really want to manage package groups, I recommend > creating a packagegroup type instead of an exec based on a grep. The exec > might be sufficient as a quick and dirty solution to get started > provisioning, but it is only one direction and if you are going to manage > lot's of package groups over time you will wish you had a type. One question on that, if create packagegroup type, logs will go out of package section... is it? I have many workarounds for solving many problems. But I'm looking for solving all my problems using native types... > > I would also recommend you manage your own repos. There is some investment > up front, but it will pay off in the long run and simplifies your change > management process significantly. Sure. I keep that in mind and is basic for our new conf. > > Cheers, > Andrew > Thanks for your replies! Arnau --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
