Re: How To Build A Perl Package Database

On Mon, Dec 17, 2012 at 9:36 AM, Tim Bunce <[email protected]> wrote:
> A separate install database for each install location seems like the only
> workable approach.

One minor complication of that is the strictest sense an "install
location" isn't all that well defined. Or perhaps I should say every
dist has 8 install locations with unspecified relationship on the
filesystem (lib, arch, bin, script, libdoc, bindoc, libhtml, binhtml).
In practice you may want to use lib *and* arch (they are never used
simultaneously, but stuff in lib may be shared over different perl
installations, contrary to arch which should be for one specific
install).

Leon