On Mon, Jan 13, 2014 at 5:17 AM, David Portabella < [email protected]> wrote:
> Hi Ryan, > > I do as follows: > > $ puppet module install puppetlabs-mysql > > $ puppet module list --tree > └─┬ puppetlabs-mysql (v2.1.0) > └── puppetlabs-stdlib (v4.1.0) > > > edit /Users/david/.puppet/modules/mysql/Modulefile > and change: > dependency 'puppetlabs/stdlib', '>= 2.2.1' > by: > dependency 'puppetlabs/stdlib', '>= 9.9.9' > > and add: > dependency 'another_inexisting_module', '>= 1.1.1' > > > $ puppet module list --tree > └─┬ puppetlabs-mysql (v2.1.0) > └── puppetlabs-stdlib (v4.1.0) > > puppet does not complain about the missing dependencies. > > > why? > what can be the problem? > Hi David. I apologize, I only now came across your reply. The gist of it is, Modulefile is the current input format for module metadata. During the operation of `puppet module build`, that metadata is transformed into the file metadata.json that Puppet, the Forge and other tools interact with. You saw this behavior because `puppet module list` was inspecting the metadata.json metadata, not the input file that you manipulated. What were you trying to accomplish with that change? Just experimenting with the dependency expressions? -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CAFkZv1sxgq%3DKH-WK3UdL9to_JTFb6kTndbYf5t1uBd-W1Etc7Q%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
