[CC'd to perl6-build]
Dan Sugalski <[EMAIL PROTECTED]> wrote:
> At 03:25 PM 8/4/00 -0700, Russ Allbery wrote:
> >Simon Cozens <[EMAIL PROTECTED]> writes:
> >
> > > Sounds good. Here's a slight modification: perllib.db is a cache;
> > > lookups take place as normal, but then any new information is
At 03:25 PM 8/4/00 -0700, Russ Allbery wrote:
>Simon Cozens <[EMAIL PROTECTED]> writes:
>
> > Sounds good. Here's a slight modification: perllib.db is a cache;
> > lookups take place as normal, but then any new information is written
> > into the cache. The cache is invalided every $configurable
Simon Cozens <[EMAIL PROTECTED]> writes:
> Sounds good. Here's a slight modification: perllib.db is a cache;
> lookups take place as normal, but then any new information is written
> into the cache. The cache is invalided every $configurable period.
Putting on my sysadmin hat, anything that a p
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.
> "SC" == Simon Cozens <[E
(Chaim, please can you *not* CC me stuff on a list you know I read! It's
not as if we don't get too much mail already from this. :)
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 an
;> re-requested.
SC> It may take just as long to parse the kpathsea configs, grovel through the
SC> lsr file and locate the thing you need. I'd have to benchmark it to be sure.
>> Actually, thinking about it. This may make automatic @INC adjustments.
>> All the core needs to f
On Fri, Aug 04, 2000 at 09:13:44AM -0400, Chaim Frenkel wrote:
> Well, the issue is how much time is spent opening directories and checking
> for entries. Also on an NFS mounted file system, the directory has to be
> re-requested.
It may take just as long to parse the kpathsea config
