Skip Menu |

This queue is for tickets about the Apache-ConfigFile CPAN distribution.

Report information
The Basics
Id: 115536
Status: new
Priority: 0/
Queue: Apache-ConfigFile

People
Owner: Nobody in particular
Requestors: RLauer [...] signatureinfo.com
Cc:
AdminCc:

Bug Information
Severity: (no value)
Broken in: (no value)
Fixed in: (no value)



Subject: Include with wildcards
Date: Wed, 22 Jun 2016 13:47:44 +0000
To: "bug-Apache-ConfigFile [...] rt.cpan.org" <bug-Apache-ConfigFile [...] rt.cpan.org>
From: "Lauer, Robert (RIS-PHL)" <RLauer [...] signatureinfo.com>
…is apparently not supported leading to: Cannot read '/etc/httpd/conf.d/*.conf': No such file or directory (do you need to define ServerRoot?) at ./apache.pl line 6 This patch seems to do the trick: --- ConfigFile.pm 2016-06-22 09:46:12.471803944 -0400 +++ /usr/share/perl5/vendor_perl/Apache/ConfigFile.pm 2001-09-18 14:31:38.000000000 -0400 @@ -102,7 +102,6 @@ use Carp; use strict; use vars qw($VERSION $AUTOLOAD); -use File::Glob ':glob'; # This is a modified VERSION that turns RCS "1.3" into "0.03" #$VERSION = do { my($r)=(q$Revision: 1.18 $=~/[\d\.]+/g); $r--; sprintf("%d.%02d", split '\.', $r)}; @@ -169,15 +168,6 @@ # add the server root unless it's a /full/path/name $file = "$server_root/$file" if $file !~ m!^/! && $server_root; - if ( $file =~/\*/ ) { - my @includes = bsd_glob($file); - my @conf; - foreach ( @includes ) { - push @conf, $self->_include($_); - } - return @conf; - } - open(CONF, "<$file") || croak("Cannot read '$file': $! (do you need to define ServerRoot?)"); chomp(my @conf = <CONF>); ---------------------------------------- The information contained in this e-mail message is intended only for the personal and confidential use of the recipient(s) named above. This message may be an attorney-client communication and/or work product and as such is privileged and confidential. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail, and delete the original message.