Please do not reply directly to this email. All additional comments should be made in the comments box of this bug.
Summary: Surprising value for --optimize in generated spec file
https://bugzilla.redhat.com/show_bug.cgi?id=739461
Summary: Surprising value for --optimize in generated spec file Product: Fedora Version: 16 Platform: Unspecified OS/Version: Unspecified Status: NEW Severity: unspecified Priority: unspecified Component: cpanspec AssignedTo: steve@silug.org ReportedBy: bochecha@fedoraproject.org QAContact: extras-qa@fedoraproject.org CC: steve@silug.org, fedora-perl-devel-list@redhat.com Classification: Fedora Story Points: --- Type: ---
Description of problem: As described in https://bugzilla.redhat.com/show_bug.cgi?id=738525#c2, here is what I get when I run: $ cpanspec ExtUtils::H2PM [... snip ...] %{__perl} Build.PL installdirs=vendor optimize="$RPM_OPT_FLAGS" [... snip ...]
$ cpanspec -m ExtUtils::H2PM [... snip ...] %{__perl} Build.PL installdirs=vendor optimize="%{optimize}" [... snip ...]
However: $ rpm --eval "%{optimize}" %{optimize}
So why is cpanspec writing %{optimize} in the generated spec file? Shouldn't it use %{optflags} instead?
Version-Release number of selected component (if applicable): cpanspec-1.78-9.fc16.noarch
How reproducible: Always.