Re: [32733] trunk/dports/perl/p5-xml-sax-expat/Portfile
On Jan 12, 2008, at 14:08, pguyot@kallisys.net wrote:
+post-activate { + system "cd ${worksrcpath} && ${build.cmd} install_sax_expat" +}
Why is something being built after the activate phase? Doesn't this mean that these items won't go into the destroot, won't show up in "port contents" and won't get uninstalled by "port uninstall"?
Le 14 janv. 08 à 11:52, Ryan Schmidt a écrit :
On Jan 12, 2008, at 14:08, pguyot@kallisys.net wrote:
+post-activate { + system "cd ${worksrcpath} && ${build.cmd} install_sax_expat" +}
Why is something being built after the activate phase? Doesn't this mean that these items won't go into the destroot, won't show up in "port contents" and won't get uninstalled by "port uninstall"?
Nope, see p5-xml-sax: post-activate { if {! [file isfile ${perl5.lib}/XML/SAX/ParserDetails.ini]} { system {perl -MXML::SAX -e "XML::SAX->add_parser(q (XML::SAX::PurePerl))->save_parsers()"} } } Every Perl XML parser writes to this file. There's something about not overwritting this file on update in p5- xml-sax; otherwise it may restore XML::SAX::PurePerl as the default parser (which as the name says, is in pure perl therefore a lot slower than the expat one). The "install_sax_expat" Makefile target does the same thing as the p5- xml-sax post-activate stage. Regards, -- Anthony Ramine, the "Ports tree cleaning Maestro". <nox@macports.org>
participants (2)
-
N_Ox
-
Ryan Schmidt