On Wednesday, September 11, 2013 11:58:55 AM UTC-5, Trevor Vaughan wrote: > > This definitely works with the best practice of not having globally > floating classes. > >
Please help me come up to speed here: why is it a best practice to avoid globally floating classes? If it truly doesn't matter when a given class is applied relative to any of the others, then how is it advantageous to declare ordering relationships for it? Does that not needlessly slow both master and agent, and make both more resource-hungry? > Are you OK with yelling at people that do though (for whatever reason)? > > Even if the assumption is that few classes are truly without ordering requirements, users should not be bullied / henpecked into declaring unneeded relationships. If it is desirable to warn users that they may have omitted needed relationships, then it is desirable to also afford them the opportunity to assert that they know better. At the coarsest level, that would mean a *continuing* ability to disable all such warnings, but ideal would be to support disabling the warnings on a class-by-class basis. John -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/puppet-dev. For more options, visit https://groups.google.com/groups/opt_out.
