Jarrod

Ooo, that was fast! Yeah that seems cool.. Except maybe use a `loop` construct to do the looping, it would be a disaster if llvm didn't optimize the recursive call....

Sorry, just woke up. That looks good -- I suggested it because autopurge is probably a highly desirable feature worth enabling at creation time. It also means I don't need...

To be clear though, it's your library and you can design it however the heck you want. The current MR definitely works as-is

> I'm pretty sure that this will require pretty significant changes to some of the ordering code, though you might be able to piggyback on the existing requisite system, since...

I would love to, but:  :( Sorry I haven't given this proposal another once-over yet, been keeping myself a little too busy. Will try to get to it since...

Just thought I'd add another datapoint: Yesterday I tried to disable some scheduled tasks that an installer enabled, as a post-install cleanup. I tried to use jinja to fetch the...

I proposed using 'nop' states to achieve that same effect because I felt it was clearer, though a little less terse. That said it seems like something people would use...

Sorry for being a bit lax here, it was a mix of not knowing if any progress was to be made, and being quite busy at my work. > @Timbus...

This is so much better and fixes my load-order issue.. Please merge it.

> I wonder if other functions not adapt to the following pull: > #8707 Oh cool. Just swinging by to report that HTTP::Client indeed needs to be updated, the retry...