Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
Summary: cpanspec doesn't escape "/" in --filter-requires leading to bad sed
Summary: cpanspec doesn't escape "/" in --filter-requires
leading to bad sed statements
CC: steve(a)silug.org, fedora-perl-devel-list(a)redhat.com
Description of problem:
cpanspec translates each "--filter-requires some_string" into a corresponding
sed statement in the corresponding perl-<module>-requires.sh of form:
However, when some_string is a path which then contains a slash "/", this
causes the sed statement to mess up.
In particular, one of the fuse modules I was compiling had some example perl
scripts which began with the line "#/usr/bin/perl." This caused the build to
then require "/usr/bin/perl" which I wanted to eliminate. When I added
"--filter-requires /usr/bin/perl", it caused *all* the sed statements to fail
with the error:
sed: -e expression #1, char 4: unknown command: `u'
Either the documentation should warn that "/" must be escaped or *better*, the
script should automatically escape the forward slashes since the user has no
reason to think that "/" is a special character (and indeed, sed could have
used just about any character to demarcate the s program)
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.