On Wed, Feb 5, 2014 at 2:20 PM, Felix Frank <felix.fr...@alumni.tu-berlin.de > wrote: > > > This resembles my feeling quite accurately. I've butted heads with > parsedfile quite a bit as well, and it can make you sad. > > Can you elaborate on the possible compatibility concerns? I don't have a > clear idea in what way those could limit re-implementations. >
I'd like to but I actually don't know yet, I haven't dug into the providers using it to see exactly what is considered the "public API". My concern was too many providers are going to override a lot of the internal functionality making it tricky to refactor to a significant deal, but that was just a worry, not actually confirmed by reality. This is just me playing around with the code and trying to get a feel for how it works in my mind and what scope we have to rework it without breaking things. I suppose this brings up a good question - does anyone reading have a custom provider based on ParsedFile that they don't have anywhere public? I'm trying to find a list of things outside of core relying on it so I can see how they are using it, and so far I only really know of inifile. -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-dev/CAPfZVDaDMPVRLx3_6MnN-gsQK-9J1y6C_24PDb7g_G3J54c7Gw%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
