On Jun 2, 2011, at 5:56 AM, Brice Figureau wrote:
> On Wed, 2011-06-01 at 22:49 -0700, Luke Kanies wrote:
>> On Jun 1, 2011, at 2:05 AM, Brice Figureau wrote:
>>
>>> On Tue, 2011-05-31 at 19:59 -0700, Luke Kanies wrote:
On May 28, 2011, at 8:11 AM, Brice Figureau wrote:
> It is imp
On Jun 3, 2011, at 5:52 PM, Daniel Pittman wrote:
> On Fri, Jun 3, 2011 at 16:18, Nick Fagerlund
> wrote:
>> (For reference: https://projects.puppetlabs.com/issues/7783)
>>
>> In 2.7, we have both a "cert" application and a new "certificate" face-
>> based app, and they both have a "generate" ac
+1
On Sun, 2011-06-05 at 09:12 +0100, R.I.Pienaar wrote:
> This allows rubygems to be used to extend or override puppet behavior.
>
> Unfortunately the features system uses the autoloader so checking for
> the rubygems feature causes a call loop. It's possible that a more
> elegant way to avoid
This allows rubygems to be used to extend or override puppet behavior.
Unfortunately the features system uses the autoloader so checking for
the rubygems feature causes a call loop. It's possible that a more
elegant way to avoid this exist rather than just checking the @path
but this did what I n
- Original Message -
> > > Also, if you are going to follow the per-compile pattern of module_dir
> > > (which seems reasonable) you should also clear the thread var (see
> > > lib/puppet/configurer.rb around line 160) so that it doesn't get
> > > stale.
> >
> > this is good I was wonde
