OK, I misunderstood you, I interpreted you were saying there was a puppet "yum" type (as in an enhanced version of the package type).
Still, this is a great approach and solves the issue. Thank you very much. Tim On Wed, Dec 31, 2008 at 12:51 PM, gary <garyy...@gmail.com> wrote: > > Hello Tim, > > You can specify a repo like this: > > [mysql-percona] > ... > enabled=1 > priority=20 > exclude=mysql-devel,... > > http://wiki.centos.org/PackageManagement/Yum/ProtectBase > http://wiki.centos.org/PackageManagement/Yum/Priorities > > I have the CentOS repos mostly set at priority 1 and then EPEL at a > lower value. If you set the Red Hat/CentOS repo priority to 1 and then > rest to a lower value, I think packages of the same name will never > get installed from lower priority repos. You may just want exclude > instead. > > The yumrepo native type also lets you specify priorty or exclusions: > > yumrepo { 'percona': > baseurl => "...", > enabled => 1, > exclude => "mysql-devel,...", > priority => ..., > ... > } > > I just started using immerda's great yum module: > > https://git.puppet.immerda.ch/ > > Manging yum repos in puppet let's you then specify package repo > requirements: > > package{ 'package': ensure => enabled, require => Yumrepo['epel'] } > > Gary > > On Jan 1, 1:11 am, "Tim Harper" <timchar...@gmail.com> wrote: >> Hi Gary, >> That sounds fantastic. I was looking for such a thing - where can I find >> it? >> >> Tim >> >> On Tue, Dec 30, 2008 at 8:06 PM, gary <garyy...@gmail.com> wrote: >> >> > Hello Tim, >> >> > Yum also supports specifying priorities and exclusions per repo. :) >> > The puppet yum repo type also lets you configure these settings. >> >> > Gary >> >> > On Dec 31, 3:26 am, "Tim Harper" <timchar...@gmail.com> wrote: >> > > Here's a breadcrumb for someone who runs into this themselves. >> >> > > I ran into an issue where I had the mysql-percona rpm's in a yum >> > repository, >> > > so yum was selecting MySQL-percona-devel when told to install >> > mysql-devel. >> > > I needed to pass the -x parameter to yum to get around it. >> > > I created a module to extend yum and give me the option to pass custom >> > > parameters: >> >> > > # >> >> > /etc/puppet/modules/package_plus_plugins/puppet/provider/package/yum_plus.rb >> > > Puppet::Type.type(:package).provide :yum_plus, :parent => :yum, :source >> > => >> > > :rpm do >> > > desc "Support via ``yum``." >> >> > > commands :yum_plus => "yum" >> >> > > def yum(*args) >> > > yum_plus(*args + @resource[:vendor].split(" ")) >> > > end >> > > end >> >> > > # then, in my manifest: >> > > package { ["mysql", "mysql-devel"]: ensure => present, provider => >> > yum_plus, >> > > vendor => "-x *percona*" } >> >> > > Criticisms / peer review welcome. >> >> > > Tim >> >> > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
