On Fri, Aug 30, 2002 at 07:33:20PM +0100, Ed Avis wrote: > Hmm. So the answer to 'what is a packlist for?' is that it might one > day be used for uninstalling, although at present it isn't. > > I would question whether packlists are the thing to use in 'make > uninstall'. Surely the makefile already knows what files are to be > removed, and where, so it can uninstall the package without looking at > the packlists.
It's sort of silly to require that you have a copy of the source code in order to uninstall a module. Having a "make uninstall" target wouldn't be the canonical way to remove a module, simply a way to address the "Shit! I didn't mean to install that there!" problem. So you still need some sort of list of what's installed in order to uninstall things once the original source tarball is gone. Why don't you just run from the assumption that packlists aren't such a hot idea and implement something else? Probably do it with Module::Build as I have no plans to do any significant changes to MakeMaker. And probably do it with YAML so we have a decent data format. -- Michael G. Schwern <[EMAIL PROTECTED]> http://www.pobox.com/~schwern/ Perl Quality Assurance <[EMAIL PROTECTED]> Kwalitee Is Job One I know you get this a lot, but you're breathtaking, like a vision of simplicity
