On 18 Feb 2011, at 11:19 AM, Daniel Pittman wrote: > On Fri, Feb 18, 2011 at 10:48, Ian Ward Comfort <[email protected]> wrote: >> Yeah, requiring just the first managed parent, as suggested, would be >> sufficient. I wasn't sure how to implement this, though, from a quick glance >> through the code. The logic that iterates over possible autorequires and >> adds relationships for anything found in the catalog is up in Puppet.Type. >> >> Any ideas for how to do that trimming? > > Nope. :) > > I was interested in characterizing the problem fully, so we understand what > the request was, but I have no idea what the solution is presently. That > part is just code, though, so how hard can it be? ;)
Heh, right. I was trying to think of a clean way to give types a way to say, "autorequire the first of these dependencies that's found in the catalog, and ignore the rest". Adding an autorequirefirst method would do it in a backwards-compatible way, but that feels icky. -- Ian Ward Comfort <[email protected]> Systems Team Lead, Academic Computing Services, Stanford University -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-dev?hl=en.
