I don't think so. I think the db should reflect the installation. The
sysadmin should be able to uninstall something. Expecting a file and
not finding it should be a fatal error. And it shouldn't keep looking.
Hmm, some care will have to be taken for setuid, etc.
<chaim>
>>>>> "SC" == Simon Cozens <[EMAIL PROTECTED]> writes:
SC> (Chaim, please can you *not* CC me stuff on a list you know I read! It's
SC> not as if we don't get too much mail already from this. :)
SC> On Fri, Aug 04, 2000 at 12:19:30PM -0400, Chaim Frenkel wrote:
>> Then how about a perllib.db. Pre-digested search paths. What %INC would
>> look like if everything and the kitchen sink were loaded. No parsing,
>> nothing but straight forward lookup code.
>>
>> If not found, or an entry not found fall back.
SC> Sounds good. Here's a slight modification: perllib.db is a cache; lookups
SC> take place as normal, but then any new information is written into the cache.
SC> The cache is invalided every $configurable period.
SC> Of course, we can do this with Perl 5, but it would be kludgy. (Remember
SC> putting subrefs into @INC?)
--
Chaim Frenkel Nonlinear Knowledge, Inc.
[EMAIL PROTECTED] +1-718-236-0183
