On Wed, Jan 19, 2011 at 20:01, Derek J. Balling wrote:
> On Jan 18, 2011, at 9:38 PM, Bostjan Skufca wrote:
>> Would anyone else fancy a wildcard path expansion in module path
>> specification?
[...]
> There are a couple potential caveats to that, the most serious being sort
> methodology for t
On Jan 18, 2011, at 9:38 PM, Bostjan Skufca wrote:
> Would anyone else fancy a wildcard path expansion in module path
> specification?
>
> Example:
>
> modulepath = /etc/puppet/modules/*
>
> ---[ above should expand to this
> equivalent ]--
> [ provided that repo
On Tue, Jan 18, 2011 at 18:38, Bostjan Skufca
wrote:
> Would anyone else fancy a wildcard path expansion in module path
> specification?
It sounds potentially useful to me, and a reasonable extension to the
current behaviour; I would usually expect this to apply to all the
various paths, not jus
Hi!
Would anyone else fancy a wildcard path expansion in module path
specification?
Example:
modulepath = /etc/puppet/modules/*
---[ above should expand to this
equivalent ]--
[ provided that repo1 and repo2 dirs exist in /etc/puppet/modules ]
modulepath = /etc/
