Jira (PUP-3236) In Puppet Gemfile, allow env var to indicate Puppet is already on load path
Title: Message Title Steve Barlow updated an issue Puppet / PUP-3236 In Puppet Gemfile, allow env var to indicate Puppet is already on load path Change By: Steve Barlow Flagged: Impediment Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3236) In Puppet Gemfile, allow env var to indicate Puppet is already on load path
Title: Message Title Nicholas Fagerlund commented on an issue Re: In Puppet Gemfile, allow env var to indicate Puppet is already on load path Christopher Price Is this change relevant to end-users or community developers, or only relevant to developers at the company? Like, what's the situation where you'd want to set PUPPET_LOADED? Add Comment Puppet / PUP-3236 In Puppet Gemfile, allow env var to indicate Puppet is already on load path We have a use case where the puppet source code is already available on the ruby load path before we run bundler, and need a way to conditionally exclude the `gem` line that references puppet. After some discussion, it sounds like an environment variable is the preferred way of doing this. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit
Jira (PUP-3236) In Puppet Gemfile, allow env var to indicate Puppet is already on load path
Title: Message Title Christopher Price created an issue Puppet / PUP-3236 In Puppet Gemfile, allow env var to indicate Puppet is already on load path Issue Type: Task Assignee: Christopher Price Created: 11/Sep/14 4:43 PM Fix Versions: 3.7.1 Priority: Normal Reporter: Christopher Price We have a use case where the puppet source code is already available on the ruby load path before we run bundler, and need a way to conditionally exclude the `gem` line that references puppet. After some discussion, it sounds like an environment variable is the preferred way of doing this. Add Comment
Jira (PUP-3236) In Puppet Gemfile, allow env var to indicate Puppet is already on load path
Title: Message Title Joshua Partlow updated an issue Puppet / PUP-3236 In Puppet Gemfile, allow env var to indicate Puppet is already on load path Change By: Joshua Partlow Flagged: Impediment Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3236) In Puppet Gemfile, allow env var to indicate Puppet is already on load path
Title: Message Title Joshua Partlow updated an issue Puppet / PUP-3236 In Puppet Gemfile, allow env var to indicate Puppet is already on load path Change By: Joshua Partlow Sprint: 2014-09-17 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3236) In Puppet Gemfile, allow env var to indicate Puppet is already on load path
Title: Message Title Joshua Partlow assigned an issue to Joshua Partlow Puppet / PUP-3236 In Puppet Gemfile, allow env var to indicate Puppet is already on load path Change By: Joshua Partlow Assignee: JoshuaPartlow Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3236) In Puppet Gemfile, allow env var to indicate Puppet is already on load path
Title: Message Title Joshua Partlow commented on an issue Re: In Puppet Gemfile, allow env var to indicate Puppet is already on load path Merged to stable in cdd5cec Add Comment Puppet / PUP-3236 In Puppet Gemfile, allow env var to indicate Puppet is already on load path We have a use case where the puppet source code is already available on the ruby load path before we run bundler, and need a way to conditionally exclude the `gem` line that references puppet. After some discussion, it sounds like an environment variable is the preferred way of doing this. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
