| Summary: | perl-File-MimeInfo doesn't build with perl-5.14.0 | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Ahmad Samir <ahmadsamir3891> |
| Component: | RPM Packages | Assignee: | Jerome Quelin <jquelin> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | ||
| Version: | Cauldron | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| URL: | https://rt.cpan.org/Public/Bug/Display.html?id=66841 | ||
| Whiteboard: | |||
| Source RPM: | perl-File-MimeInfo | CVE: | |
| Status comment: | |||
|
Description
Ahmad Samir
2011-06-16 05:18:13 CEST
- patch added to package. - perl scripts installed in /usr/bin have their shebang line replaced with the exact path to the perl that built the package. and adding a perlapi requires would not work, since it *also* breaks on minor perl upgrades. we need to rebuild all of those every time there's a perl upgrade. i need to check whether it's possible to keep /usr/bin/perl in the shebang line Status:
NEW =>
RESOLVED OK, thanks for the clarification. fyi - i've committed in svn+ssh://svn.mageia.org/svn/packages/cauldron/perl/current a script named find-need-rebuild which will find all packages providing a perl script with a wrong shebang. That should improve things. The problem is, it'll only catch installed packages, but usually there're many uninstalled packages than installed ones. indeed, but there's no way to know the shebang used by a non-installed package. note however that i have almost all perl packages installed locally. (All of them? great, that should work then :)). |