Well, apparently nobody knows an easy solution.<div><br></div><div>I
ended up create my own ruby-enterprise-mysql rpm package, and all my
troubles went away. (though this is still an issue I'd like to know
the answer to).</div><div><br></div><div>Tim<br><br><div
class="gmail_quote">On Tue, Dec 30, 2008 at 8:36 AM, Tim Harper <span
dir="ltr"><[email protected]></span> wrote:<br><blockquote
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc
solid;padding-left:1ex;"><p>I'm running in to an issue where I want to
install a gem named "mysql" and an rpm named "mysql". Puppet
complains about this when I've got bot directives in there, saying
Package['mysql'] is already defined.</p>
<p>I've tried using the alias command to alias them as mysql-rpm, and
mysql-gem. Puppet still complained about Package['mysql'] being
defined twice. Also tried this:</p>
<p>package { "mysql-gem": name => "mysql", provider => gem ...<br>
package { "mysql-rpm": name => "mysql", provider => yum ...</p>
<p>This also complained. Does anyone suggestions on how to overcome
this? Can I use a suffix of somekind specific to the package
attributes (like arch or version) to help puppet distinguish between
the two.. or do I need to write my own "gem" type definition?</p>
<p>Thanks!</p>
<p>Tim</p>
</blockquote></div><br></div>
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
