Summary: | g-cpan cannot install XML::SAX::Expat | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Dan A. Dickey <dan.dickey> |
Component: | Current packages | Assignee: | Gentoo Perl team <perl> |
Status: | RESOLVED CANTFIX | ||
Severity: | normal | ||
Priority: | High | ||
Version: | 2006.0 | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Dan A. Dickey
2006-11-09 10:54:56 UTC
This is actually a "bug" with the module itself, not g-cpan. The issue here would be an issue if we provided this ebuild in portage vice g-cpan - line 698ish of the generated Makefile (install_sax_expat :) is attempting to write to a file while still inside the sandbox (which means the env it sees and the env available don't quite match, so what it's trying to call isn't where it thinks it is yet). If we had created an ebuild for this, we probably would have had to disable this line and done an einfo to the user to run perl -MXML::SAX -e "XML::SAX->add_parser(q(XML::SAX::Expat))->save_parsers()" if they wanted to switch parsers. Closing this as CAN'T FIX since it isn't a g-cpan bug (and the conversation that brought this up is elsewhere and still debating) |