James.FitzGibbon <James.FitzGibbon@target.com> writes: > >The best solution I can see right now is to ensure that all old files of a >distribution are deleted prior to overlaying the new module into sitelib, but >this requires that an accurate list of all files installed in the past be >available, which isn't always the case. The .packlist file is pretty good these days. > >I don't see any simple solution to this other than to be extra vigilant when >upgrading, and hoping that the module author points out this subtle gotcha in >the ChangeLog of their module. Another option would be for a module which lost its XS to still insist it was installed in archlib. > >Any thoughts to the contrary are welcome.Thread Previous