On 4 July 2014 22:14, David Schmitt da...@dasz.at wrote:
On 2014-07-04 18:31, Erik Dalén wrote:
Due to the dynamic scoping of them I only really use them for setting
global defaults. And some mechanism for doing that is really needed.
I've used to do that to set file buckets and Exec#path.
Oh, and another insight - there is a desire to be able to specify the
same resource multiple times - if the values are the same, or augmenting
values then it is not a conflict. This will require the new catalog
builder we have been sketching on since it has a richer catalog model.
It just
there is a desire to be able to specify the same resource multiple times -
if the values are the same, or augmenting values then it is not a conflict
Yes, please! I've wanted this for years!
Trevor
On Tue, Jul 8, 2014 at 7:05 AM, Henrik Lindberg
henrik.lindb...@cloudsmith.com wrote:
Oh,
I've skipped everything else about these messages to beg for this too, this
is the single most important change we can make to the language to allow
users to use modules off the forge more easily.
On Tue, Jul 8, 2014 at 8:31 AM, Trevor Vaughan tvaug...@onyxpoint.com
wrote:
there is a desire to
On 2014-08-07 16:55, Ashley Penney wrote:
I've skipped everything else about these messages to beg for this too,
this is the single most important change we can make to the language to
allow users to use modules off the forge more easily.
Hear ya, load and clear. The first cut of the new
On Sunday, July 6, 2014 8:26:28 PM UTC-5, henrik lindberg wrote:
Thank you everyone that commented on the first RFC for Resource Defaults
(and Collection) - some very good ideas came up. I am creating a new
thread because I wanted to take the Collection part in a separate
discussion
On 2014-08-07 18:09, John Bollinger wrote:
On Sunday, July 6, 2014 8:26:28 PM UTC-5, henrik lindberg wrote:
Thank you everyone that commented on the first RFC for Resource
Defaults
(and Collection) - some very good ideas came up. I am creating a new
thread because I wanted to
Just a heads up to facter contributors that we've synced the facter-2
branch to master and are retiring the facter-2 branch. This means that
facter contributions should return to the normal behavior of targeting
master (or stable for .z targeted fixes).
For background on how we ended up with a
