in reply to Problems Updating HTML::Parser

PPM uses HTML::Parser which causes it to load Parser.dll which prevents you from removing it. It looks like PPM tries to deal with upgrading modules that it uses, but it probably can't deal with such modules including a *.dll. FYI, my copy of HTML::Parser doesn't include a *.dll, but perhaps that is because it is extra old.

So PPM probably needs to be updated to fix this problem now that one of the modules it uses includes a *.dll.

The "easiest" way I can think to work around this would be to copy the "site" directory tree somewhere, then use "perl -IcopyOfSite -S ppm" to launch ppm but have it use the copy rather than the original. I'd hope that it would still install to the regular place and so would find Parser.dll not in use. Then delete copyOfSite when done.

        - tye (but my friends call me "Tye")
  • Comment on (tye)Re: Problems Updating HTML::Parser

Replies are listed 'Best First'.
Re: (tye)Re: Problems Updating HTML::Parser
by gellyfish (Monsignor) on Mar 01, 2002 at 22:53 UTC

    does it use HTML::Parser ? It definitely uses *XML::Parser* for sure, but I would think that the likely explanation is that some other process is using HTML::Parser.

    HTML::Parser has had an XS component and hence a Parser.dll since version 3.0 BTW

    /J\

      Both XML-Parser and HTML-Parser are included in the list of modules that PPM uses (search for "PPMPRECIOUS" in ppm.bat). I didn't search any further to see what part of PPM uses HTML::Parser nor how/why. Feel free to.

              - tye (but my friends call me "Tye")

        Hmm, the versions on CPAN certainly don't use it directly:

        [root@orpheus build]# find PPM PPM-2.1.1 -type f -print | xargs grep ' +HTML::Parser' [root@orpheus build]#
        I don't have an actual Activestate distribution to hand to check unfortunately. I think that what it might be is that PPM uses LWP and HTML::Parser is a dependency of that.

        /J\