Yeah, I'm saying you probably have a specific mysql module in mind and it seems the only way that dependency is specific enough is through the Modulefile.
In my manifest I'd just say "include mysql". There's no mechanism in the language itself for deciphering between someuser-mysql and someuser2-mysql, right? It seems the only thing that specifies the difference is the Modulefile and thus the puppet module tool. What if I choose someuser1-mysql for mymodule and then I later want another module on the forge that chose someuser2-mysql as it's dependency? Now if they don't have similar interfaces (not to mention implementations) I'm stuck, right? Thanks Mark On Thursday, August 16, 2012 2:35:57 PM UTC-4, Ryan Coleman wrote: > > On Thu, Aug 16, 2012 at 11:05 AM, Mark Roggenkamp > <mark.ro...@gmail.com <javascript:>> wrote: > > What happens when a module (mymodule) depends on the "mysql" module but > you > > chose a mysql module that isn't quite the same as the one mymodule > expects? > > Your module would depend on a specific mysql module though, right? > mymodule depends on someuser-mysql for example. > > When you're authoring your own content, you'll have to make a decision > about which users mysql module meets your needs and aligns with how > you view the world. We don't have great tooling on the Forge to help > you make that decision but we'll be rectifying that. > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/tnJ4P-GWIgEJ. 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.
