-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
(Coming late to the discussion, I know. Sorry.)
On 2012-01-26 11:19, Felix Frank wrote:
[Regarding common modules for installing packages.]
> Thinking about other examples of similar systems (CPAN, Gems, Pear, you
> name it), module dependencies ar
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
(I know I'm late in responding; I'm a couple of months behind in reading
the mailing-list, and still have 2000 unread. I have read this entire
thread, though.)
On 2012-01-19 18:18, Nigel Kersten wrote:
> I'm looking for strong opinions on whether we
On 01/26/2012 11:21 AM, Nick wrote:
> For example, suppose in one place I need a file to exist, and in another I
> also
> need it to be executable. Oh dear, I can't do that.
That, and you'd need to merge require/before etc. Such things aren't
trivial. Nan put it this way:
On 01/25/2012 03:59 PM
On 26/01/12 01:25, Ashley Penney wrote:
> All I know is that telling users "If you download 5 modules from puppet forge
> make sure you go through them all, extract any duplicating resources into
> random modules that exist purely to allow you to realize packages" instead
> leads
> to a really bad
On 26/01/12 00:55, Trevor Vaughan wrote:
> I mentioned in a previous thread that I don't see an issue with having
> multiple identical resources compiled across the code base and I'd like to add
> that to this thread since it's related.
>
> class a {
> package { 'foo': ensure => 'present' }
> }
Hi,
On 01/26/2012 02:25 AM, Ashley Penney wrote:
> This is a fantastic reply and I appreciate the work you put into it. I
> have just one
> question. As it stands functions can only apply to partial catalogs and
> not to the
> full catalog. Is this a fundamental design decision that cannot be
>
On Wed, Jan 25, 2012 at 5:25 PM, Ashley Penney wrote:
>
> All I know is that telling users "If you download 5 modules from puppet
> forge
> make sure you go through them all, extract any duplicating resources into
> random modules that exist purely to allow you to realize packages" instead
> lead
This is a fantastic reply and I appreciate the work you put into it. I
have just one
question. As it stands functions can only apply to partial catalogs and
not to the
full catalog. Is this a fundamental design decision that cannot be
changed? Perhaps
it would be interesting to speculate on wha
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jeff,
Thanks for the concise write-up, it was really helpful for parsing through all
of the different arguments.
I would like to second the idea that Aaron Grewell had earlier that some sort
of exception handling be allowed and that some other meth
On Thu, Jan 19, 2012 at 9:18 AM, Nigel Kersten wrote:
> I'm looking for strong opinions on whether we should or shouldn't deprecate
> the defined() function for Telly, the next major Puppet release this year.
>
> jcbollinger put it quite well in another thread:
>
> "Use of the "defined" function i
Hi Dan,
sorry if I come around bluntly about this, but:
On 01/20/2012 10:00 AM, Dan Bode wrote:
> * static resources in a defined resource type (avoids having to use
> classes to store all static dependencies)
>
> * the big reason I keep on leaning on it is for package dependencies.
> Often some
How about deprecating defined?(Type['title']), but allowing it to accept a
resource hash? This would definitely satisfy my use cases while alleviating
concerns about resource attribute conflicts/parse order dependencies
if defined?(
{
package['foo'] => { ensure => present }
}
) {
package
I wind up using defined more than I should probably admit. yes it is
dangerous/confusing b/c of parse order dependencies, but it is also really
useful for a few use cases
* static resources in a defined resource type (avoids having to use classes
to store all static dependencies)
* the big reason
+1 to ditch it. As the other thread said well: use of defined() is
only done in badly designed code. Getting rid of it will force people
to use better designs.
cheers,
Walter Heck
On Thu, Jan 19, 2012 at 19:19, R.I.Pienaar wrote:
>
>
> - Original Message -
>> I'm looking for strong opin
- Original Message -
> I'm looking for strong opinions on whether we should or shouldn't
> deprecate the defined() function for Telly, the next major Puppet
> release this year.
First choice would be to make it reliable, that seems unlikely though
+1, I'd also make the scope.classes var
I'm looking for strong opinions on whether we should or shouldn't deprecate
the defined() function for Telly, the next major Puppet release this year.
jcbollinger put it quite well in another thread:
"Use of the "defined" function introduces a parse-order dependency, and the
additional work you n
16 matches
Mail list logo
