On Thu, Jan 23, 2014 at 12:16 AM, Erik Dalén <[email protected]>wrote:
> > > > On 22 January 2014 21:01, Ashley Penney <[email protected]> wrote: > >> On Wed, Jan 22, 2014 at 1:15 PM, Henrik Lindberg < >> [email protected]> wrote: >> >>> Recent Pull Requests to puppetlabs-stdlib has raised issues w.r.t how we >>> should handle stdlib going forward. We have also had a discussion about >>> types and providers in core and if they should be moved out to modules in a >>> "tier2". That discussion also raises issues about >>> backwards compatibility, and configuration of modules. >>> >>> I am posting this to trigger a discussion and to collect requirements. >>> >> >> I figured I'd have a stab at some answers to get the ball rolling. >> >> >>> * Is there content in stdlib that really belongs in core? >>> >> >> Well, the validation stuff does and is covered by your type system, >> moving forward. >> >> The stuff I would argue belongs in the core (and almost certainly >> redesigned from what's in stdlib) are: >> >> 1) Validation, which comes in with the type system. We have all the >> validate() and is_*() functions in stdlib. >> 2) Better ways to get information from other parts of puppet: things >> like getparam() in order >> to be able to reach into a define for a value, getvar(), >> get_module_path(), >> 3) Better ways to handle duplicate resources: We have ensure_packages, >> ensure_resources, all hacks to deal with duplication. >> 4) Iteration over certain data. We know future parser has iteration >> which solves most of this and the only other use cases are the has_*() >> functions which will mostly be replaced by structured data and iteration. >> >> These were the things where we've got multiple functions and so they feel >> like language issues to me. The rest is mostly genuine stdlib stuff. >> > > The to_bytes() function (which I added) is mostly there due to issues with > Facter, that it prints human readable memory and disk sizes instead of > machine readable ones. But perhaps this can be solved with Facter 2.0 so > this function could eventually be removed or moved into its own module if > people really want it. > > I think that issue was solved inside facter. I see that facter 1.7.4 has memorysize_mb and family. > -- > Erik Dalén > > -- > 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 [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/puppet-dev/CAAAzDLdYHdu4t1dun8jA_2bem-5WMSbPuu4%3DRT4Fjos%2Bq_xG%3Dw%40mail.gmail.com > . > > For more options, visit https://groups.google.com/groups/opt_out. > -- Andrew Parker [email protected] Freenode: zaphod42 Twitter: @aparker42 Software Developer *Join us at PuppetConf 2014, September 23-24 in San Francisco* -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-dev/CANhgQXsW70ftz%3DYRiaJqEyFmMJjZ%3DjfAHUheOh%2B7ULpSnaw-tw%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
