On Fri, 30 Aug 2002, Michael G Schwern wrote: >>It needs to be decided: should there be a canonical way to remove a >>module? > >There are few things which are canonical in Perl. There are merely things >people put lots of effort into and people liked enough to make it >ubiquitous. > >In other words: Just Do It Already
So your decision is Yes, it must be possible to uninstall a module without needing its source code. But I assume this is a requirement for Module::Build - not something you plan to add (or re-add) to MakeMaker. >As Nick pointed out, MakeMaker already has a packlist based >uninstaller. ExtUtils::Install::uninstall(). It even has an >uninstall target which uses it, but it's deprecated. I forget why >it's deprecated. If someone wants to investigate and undeprecate it >I'd accept that. I'll have a look some time. I'd expect, however, that it was deprecated because it no longer works. >Otherwise, I'd rather just leave packlists as they are and extend >Module::Build instead. What I am getting at is: if I want to contribute a patch to MakeMaker, do I need to worry about packlists? And if so, what should be the convention for packlists in directories not owned by perl, such as /usr/share/doc/? -- Ed Avis <[EMAIL PROTECTED]>
