On Sun, Sep 1, 2013 at 10:07 AM, Dustin J. Mitchell wrote:
> First let me apologize for *not* submitting my patches upstream (and
> thanks, Christian, for merging them!). Given the appearance of
> "Puppet" throughout the library, I assumed that it had actually been
> forked, not vendored. Not th
On 2013-03-09 22:46, Andy Parker wrote:
On Tue, Sep 3, 2013 at 12:53 PM, Luke Kanies mailto:l...@puppetlabs.com>> wrote:
How difficult would it be to build tools to help our users
understand when they might be making a mistake in this area?
Warning is easy. Warning correctly is hard. W
On Sep 3, 2013, at 12:06 PM, Andy Parker wrote:
> On Tue, Sep 3, 2013 at 11:34 AM, Drew Blessing
> wrote:
> I've been following this discussion for some time. As it progressive I've
> found myself fighting internally, going one way and then the other about how
> this should really be. I keep
Just an update for everyone. The problem with validating that the referenced
resource is in the catalog now has a solution (for the most part). You’d need
to take advantage of the new `post_compile_hook` that should be supported in
future versions of Puppet. I may write up a helper module later
On Sep 3, 2013, at 12:00 PM, Eric Sorenson wrote:
> Replies inline; I've butchered the quoting but will try to keep the
> attribution correct.
>
> [John Bollinger] Part of my premise here is that you cannot reasonably infer
> from a class declaration alone -- regardless of the form of the decl
On Tue, Sep 3, 2013 at 12:53 PM, Luke Kanies wrote:
> On Sep 3, 2013, at 12:06 PM, Andy Parker wrote:
>
> On Tue, Sep 3, 2013 at 11:34 AM, Drew Blessing
> wrote:
>
>> I've been following this discussion for some time. As it progressive I've
>> found myself fighting internally, going one way and
On Sep 3, 2013, at 12:30 PM, Jeff McCune wrote:
> On Tue, Sep 3, 2013 at 12:00 PM, Eric Sorenson
> wrote:
> [Andy] Here are the possibilities:
> * resource like syntax for classes expresses containment:
> class container { class { contained: parameter => value } }
> * a function decla
On Tue, Sep 3, 2013 at 12:00 PM, Eric Sorenson wrote:
> [Andy] Here are the possibilities:
>>
> * resource like syntax for classes expresses containment:
>>
>> class container { class { contained: parameter => value } }
>>
>> * a function declares the class *and* expresses containment
>
I've been following this discussion for some time. As it progressive I've
found myself fighting internally, going one way and then the other about
how this should really be. I keep coming back to the same place - this is
a bug and Luke's original statement is very important:
The fix should re
On 3 September 2013 15:00, Eric Sorenson wrote:
> Replies inline; I've butchered the quoting but will try to keep the
> attribution correct.
>
>
>> [Andy] Here are the possibilities:
>>
> * resource like syntax for classes expresses containment:
>>
>> class container { class { contained: p
Replies inline; I've butchered the quoting but will try to keep the
attribution correct.
[John Bollinger] Part of my premise here is that you cannot reasonably
> infer from a class declaration alone -- regardless of the form of the
> declaration -- whether its declaring class intends to contain
On Sun, Sep 1, 2013 at 9:40 AM, Dustin J. Mitchell wrote:
> It's not quite *static* content. I can see a lot of ways that this
> might be useful to users. For example, I host yum/apt/DMG repos (and
> maybe nuget too!) on my puppet masters, and as I scale puppet masters
> I will want to use shar
On Tue, Sep 3, 2013 at 11:34 AM, Drew Blessing wrote:
> I've been following this discussion for some time. As it progressive I've
> found myself fighting internally, going one way and then the other about
> how this should really be. I keep coming back to the same place - this is
> a bug and Luk
On Sun, Sep 1, 2013 at 10:53 AM, Dustin J. Mitchell wrote:
> First, a vote against reverting to explicit loading -- the module
> autoloader is *awesome* from a user perspective.
>
>
Exactly. I don't think reverting to explicit loading would be a win for
users.
> Second, to the idea of doing a be
On Sun, Sep 1, 2013 at 9:52 AM, Dustin J. Mitchell wrote:
> The switch to semantic versioning has been pretty broadly announced
> and discussed. It will benefit from being seen in action, and from a
> smooth start. Which means sooner rather than later, and fewer
> compatibility breakages rather
On Mon, Sep 2, 2013 at 1:07 PM, Dustin J. Mitchell wrote:
> On Mon, Sep 2, 2013 at 12:40 PM, Henrik Lindberg
> wrote:
> > How would you ensure this? The fact that it seems to work? Do you have
> > perfect test coverage? (The parser checks all code paths, not just the
> ones
> > that are executed
Going forward I'm going to aim for this twice a month as weekly is too
frequent and I forget to write them every week.
This update is dedicated to blkperl who keeps me writing them by reminding
me every time I forget.
It's been a busy month and with Puppetconf falling in the middle of the
month p
On Tuesday, September 3, 2013 6:15:39 AM UTC-5, Sean Millichamp wrote:
>
> On Mon, 2013-09-02 at 23:50 -0700, Luke Kanies wrote:
>
> > However, I still disagree that fixing bugs should constitute a change
> > worth upping a major rev. If it's a bug, then fixing it shouldn't be
> > an incompat
On Mon, 2013-09-02 at 23:50 -0700, Luke Kanies wrote:
> However, I still disagree that fixing bugs should constitute a change
> worth upping a major rev. If it's a bug, then fixing it shouldn't be
> an incompatibility, should it?
I would argue that it has been the behavior for so long that fixin
On Aug 30, 2013, at 5:13 PM, markus wrote:
>
>> But I also don't think there's fundamentally anything *wrong* with
>> using whits, since they accurately model the notion of containment,
>> with respect to order: classes have a "start", and a "finish", and
>> there's stuff in between. It doesn't
On Aug 30, 2013, at 4:35 PM, Nick Lewis wrote:
> On Friday, August 30, 2013 at 3:58 PM, Luke Kanies wrote:
>> On Aug 30, 2013, at 10:47 AM, Andy Parker wrote:
>>
>>> On Fri, Aug 30, 2013 at 10:24 AM, Luke Kanies wrote:
>>> On Aug 30, 2013, at 9:11 AM, Andy Parker wrote:
>>>
On Fri, Aug
21 matches
Mail list logo
