On Oct 3, 2008, at 10:22 AM, dd-b wrote: > > Which cause errors (multiple definitions largely). > > One solution is to explicitly say "include class/*.pp" (if all the > class files you want to pick up are in fact .pp files). Since the > backup suffix goes at the very end, backup files fail to match the > more specific patter; and people reading the code will clearly see > that only .pp files are being included. > > All the examples show just "include class/*", so I was using that > until I started getting errors. I deduce that none of the heavy > contributors have backup files enabled :-). Since I come from a > TOPS-20 background, I'm used to the idea of having the last few > versions of a file I saved be available in the directory; and using ls > switches and bash switches I hide them from myself most of the time, > so they don't make my directories too messy to bear (as *I* see > them). > > I'm not sure anything should be changed; I'm posting so anybody > searching for this "problem" might find information.
I agree with Peter that an SCM is the right answer for backup files -- if you're not using one, um, you make some kind of sign to ward off evil and adopt one immediately. Additionally, I highly recommend against the old-style 'class' directory -- IMO, it's been entirely superceded by modules. -- If computers get too powerful, we can organize them into a committee -- that will do them in. -- Bradley's Bromide --------------------------------------------------------------------- Luke Kanies | http://reductivelabs.com | http://madstop.com --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
