On Wed, 3 Mar 2010 12:46:05 -0800, Eric Sorenson wrote:
> This might just be a style nitpick, but why anchor the start and then .*
> match? Just start your regexp where you want the match to start. You
have
> a nice anchor at the end so the regexp will optimize backwards from
there.
> Compare re
This might just be a style nitpick, but why anchor the start and then .* match?
Just start your regexp where you want the match to start. You have a nice
anchor at the end so the regexp will optimize backwards from there. Compare
readability:
On Mar 3, 2010, at 9:09 AM, James Cammarata wrote:
On Wed, 03 Mar 2010 18:01:33 +0100, Brice Figureau
wrote:
>
> You're seeing bug #3229:
> http://projects.reductivelabs.com/issues/3229
>
> The workaround until we fix the issue is to write your regex in lower
> case:
> package { "kernel-development":
>> ensure => "present",
>> name => $
Hi,
On Wed, 2010-03-03 at 10:50 -0600, James Cammarata wrote:
> I'm trying to use regex to install the appropriate kernel-devel packaged,
> based on what kernel the system has installed, running puppet-0.25.3-2
> (EPEL version for RHEL4).
>
> Here is what I'm doing:
>
> package { "kernel-dev
I'm trying to use regex to install the appropriate kernel-devel packaged,
based on what kernel the system has installed, running puppet-0.25.3-2
(EPEL version for RHEL4).
Here is what I'm doing:
package { "kernel-development":
ensure => "present",
name => $kernelrelease ? {
/^(
