Front page | perl.perl5.porters |
Postings from October 2003
On Mon, Oct 06, 2003 at 10:42:30AM -0500, James.FitzGibbon wrote: > Question: if a module started it's life with XS components and a subsequent > upgrade removes those components and makes the module pure-perl, then is > there any mechanism to ensure that the new version is loaded? At the user's end they can do: make install UNINST=1. That's what I have CPAN.pm set to do. It just searches @ISA for other copies of the same file. Something more elaborate might involve .packlists. For a little bit of fun, look at the little known instmodsh that comes with ExtUtils::MakeMaker. Also ExtUtils::Install has a packlist-based uninstall() function. However, all versions of SQL::Statement might not be in the .packlist. For example, Debian doesn't use packlists in their packaged Perl modules (something I might have to talk to them about). UNINST=1 is a pretty good way from the module user's perspective.Thread Previous | Thread Next