Have an exec that will execute the enable repo, have it depend on the yumrepo config, and also have a package depend on the exec, then have another exec subscribing to the package to disable the repo? Thats only my guess for now. I agree with the comments in the ticket, manage internal repos, only add what you want. otherwise, you run into headaches.
On May 20, 2009, at 8:45 PM, Ben wrote: > > chakkerz wrote: >> Hello there >> >> At this stage i have epel deployed to all new hosts, but it's >> disabled >> by default. In short i don't fully trust the repo (and i'll look into >> it further and this may render this post irrelevant for now), but: >> >> how can i deploy packages from an optional, and by default disabled >> repo? using the packages type, i mean i could use exec, but that >> would >> require me to know something about what the package contains which >> could make it a lot of work, unless i want puppet to constantly run >> the command... >> >> Cheers >> chakkerz >>> >> >> > I requested this feature but it was rejected. > > http://projects.reductivelabs.com/issues/2247 > > Ben > > > > --~--~---------~--~----~------------~-------~--~----~ 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 this group, send email to puppet-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
