Description of problem: In all my recent perl-related package submissions, the reviewer has suggested to me to use the plain `perl` command instead of the `%{_perl}` macro. For example: %build -%{__perl} Makefile.PL INSTALLDIRS=vendor OPTIMIZE="%{optflags}" +perl Makefile.PL INSTALLDIRS=vendor OPTIMIZE="%{optflags}" make %{?_smp_mflags} Now, of course I'll try to pay more attention to it, or else reviewers will be tired of always repeating the same thing. :) However, it would be very helpful if cpanspec could create specfiles which directly respect our experts' recommendations, so that we don't have to change it for every package. This is with: cpanspec-1.78-12.fc18.noarch
Have you found and refs for this? Only things I found related in the packaging guidelines: https://fedoraproject.org/wiki/Packaging:Perl shows it as %{__perl} and not perl. I would recommend asking the perl-sig folks to see what the thought is on this. and if going to perl from %{__perl} is the desired path going forward, let's get it changed on the guidelines page and then we can work on getting a change upstream into cpanspec.
Main packaging guidelines discourage using macros for plain commands <https://fedoraproject.org/wiki/Packaging:Guidelines#Macros>: Macro forms of system executables SHOULD NOT be used except when there is a need to allow the location of those executables to be configurable. For example, rm should be used in preference to %{__rm}, but %{__python} is acceptable.
(In reply to comment #2) > Main packaging guidelines discourage using macros for plain commands > <https://fedoraproject.org/wiki/Packaging:Guidelines#Macros>: > > Macro forms of system executables SHOULD NOT be used except when there is a > need to allow the location of those executables to be configurable. For > example, rm should be used in preference to %{__rm}, but %{__python} is > acceptable. a) %__perl is in a similar position as %__python. b) The wording "SHOULD NOT" means %__perl or other macros are _allowed_ => It's up to a packager's discretion to use it or not. I encourage people to use it and consider people enforcing plain "perl" to commit a mistake.
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '18'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 18's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.