On Wed, Dec 10, 2014 at 10:27 AM, John Bollinger <john.bollin...@stjude.org> wrote:
> Additionally, avoiding hardcoded paths and avoiding the assumption that > Puppet has a private Ruby to play around in will be helpful (and wise in > any case). > If the best predictor of future behavior is past behavior then our components will make assumptions about hardcoded paths and the location of specific dependencies like Ruby, Java, etc... I don't think it's possible to avoid this outcome given the number of people and teams working on the various projects and the desire to reduce the complexity of the system. Do you have a sense of how much impact this will be on you John? -Jeff -- 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 puppet-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-dev/CAOXx1vERt3Owev-r6MxzVyK6qids%2BH9bMAdew8qzqsMN%3DoAeWw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
