This file is indexed.

/usr/share/doc/cl-asdf/asdf/Caching-Results.html is in cl-asdf 2:3.3.1-1.

This file is owned by root:root, with mode 0o644.

The actual contents of the file can be viewed below.

  1
  2
  3
  4
  5
  6
  7
  8
  9
 10
 11
 12
 13
 14
 15
 16
 17
 18
 19
 20
 21
 22
 23
 24
 25
 26
 27
 28
 29
 30
 31
 32
 33
 34
 35
 36
 37
 38
 39
 40
 41
 42
 43
 44
 45
 46
 47
 48
 49
 50
 51
 52
 53
 54
 55
 56
 57
 58
 59
 60
 61
 62
 63
 64
 65
 66
 67
 68
 69
 70
 71
 72
 73
 74
 75
 76
 77
 78
 79
 80
 81
 82
 83
 84
 85
 86
 87
 88
 89
 90
 91
 92
 93
 94
 95
 96
 97
 98
 99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
<!-- This manual describes ASDF, a system definition facility
for Common Lisp programs and libraries.

You can find the latest version of this manual at
https://common-lisp.net/project/asdf/asdf.html.

ASDF Copyright (C) 2001-2016 Daniel Barlow and contributors.

This manual Copyright (C) 2001-2016 Daniel Barlow and contributors.

This manual revised (C) 2009-2016 Robert P. Goldman and Francois-Rene Rideau.

Permission is hereby granted, free of charge, to any person obtaining
a copy of this software and associated documentation files (the
"Software"), to deal in the Software without restriction, including
without limitation the rights to use, copy, modify, merge, publish,
distribute, sublicense, and/or sell copies of the Software, and to
permit persons to whom the Software is furnished to do so, subject to
the following conditions:

The above copyright notice and this permission notice shall be
included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE
LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION
OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
 -->
<!-- Created by GNU Texinfo 6.5, http://www.gnu.org/software/texinfo/ -->
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<title>Caching Results (ASDF Manual)</title>

<meta name="description" content="Caching Results (ASDF Manual)">
<meta name="keywords" content="Caching Results (ASDF Manual)">
<meta name="resource-type" content="document">
<meta name="distribution" content="global">
<meta name="Generator" content="makeinfo">
<link href="index.html#Top" rel="start" title="Top">
<link href="Concept-Index.html#Concept-Index" rel="index" title="Concept Index">
<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
<link href="Controlling-where-ASDF-searches-for-systems.html#Controlling-where-ASDF-searches-for-systems" rel="up" title="Controlling where ASDF searches for systems">
<link href="Configuration-API.html#Configuration-API" rel="next" title="Configuration API">
<link href="Search-Algorithm.html#Search-Algorithm" rel="prev" title="Search Algorithm">
<style type="text/css">
<!--
a.summary-letter {text-decoration: none}
blockquote.indentedblock {margin-right: 0em}
blockquote.smallindentedblock {margin-right: 0em; font-size: smaller}
blockquote.smallquotation {font-size: smaller}
div.display {margin-left: 3.2em}
div.example {margin-left: 3.2em}
div.lisp {margin-left: 3.2em}
div.smalldisplay {margin-left: 3.2em}
div.smallexample {margin-left: 3.2em}
div.smalllisp {margin-left: 3.2em}
kbd {font-style: oblique}
pre.display {font-family: inherit}
pre.format {font-family: inherit}
pre.menu-comment {font-family: serif}
pre.menu-preformatted {font-family: serif}
pre.smalldisplay {font-family: inherit; font-size: smaller}
pre.smallexample {font-size: smaller}
pre.smallformat {font-family: inherit; font-size: smaller}
pre.smalllisp {font-size: smaller}
span.nolinebreak {white-space: nowrap}
span.roman {font-family: initial; font-weight: normal}
span.sansserif {font-family: sans-serif; font-weight: normal}
ul.no-bullet {list-style: none}
-->
</style>


</head>

<body lang="en">
<a name="Caching-Results"></a>
<div class="header">
<p>
Next: <a href="Configuration-API.html#Configuration-API" accesskey="n" rel="next">Configuration API</a>, Previous: <a href="Search-Algorithm.html#Search-Algorithm" accesskey="p" rel="prev">Search Algorithm</a>, Up: <a href="Controlling-where-ASDF-searches-for-systems.html#Controlling-where-ASDF-searches-for-systems" accesskey="u" rel="up">Controlling where ASDF searches for systems</a> &nbsp; [<a href="index.html#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="Concept-Index.html#Concept-Index" title="Index" rel="index">Index</a>]</p>
</div>
<hr>
<a name="Caching-Results-1"></a>
<h3 class="section">8.9 Caching Results</h3>

<p>The implementation is allowed to either eagerly compute the information
from the configurations and file system, or to lazily re-compute it
every time, or to cache any part of it as it goes.
In practice, the recommended <code>source-registry</code> eagerly collects and caches results
and you need to explicitly flush the cache for change to be taken into account,
whereas the old-style <code>*central-registry*</code> mechanism queries the filesystem every time.
</p>
<p>To explicitly flush any information cached by the system
after a change was made in the filesystem, See <a href="Configuration-API.html#Configuration-API">Configuration API</a>,
and e.g. call <code>asdf:clear-source-registry</code>.
</p>
<p>Starting with ASDF 3.1.4, you can also explicitly build a persistent cache
of the <samp>.asd</samp> files found under a tree:
when recursing into a directory declared by <code>:tree</code> and its transitive subdirectories,
if a file <samp>.cl-source-registry.cache</samp> exists containing a form
that is a list starting with <code>:source-registry-cache</code> followed by a list of strings,
as in <code>(:source-registry-cache <em>&quot;foo/bar.asd&quot; &quot;path/to/more.asd&quot; ...</em>)</code>,
then the strings are assumed to be <code>unix-namestring</code>s designating
the available asd files under that tree, and the recursion otherwise stops.
The list can also be empty, allowing to stop a costly recursion in a huge directory tree.
</p>
<p>To update such a cache after you install, update or remove source repositories,
you can run a script distributed with ASDF:
<code>tools/cl-source-registry-cache.lisp <em>/path/to/directory</em></code>.
To wholly invalidate the cache, you can
delete the file <samp>.cl-source-registry.cache</samp> in that directory.
In either case, for an existing Lisp process to see this change,
it needs to clear its own cache with e.g. <code>(asdf:clear-source-registry)</code>.
</p>
<p>Developers may safely create a cache in their development tree,
and we recommend they do it at the top of their source tree if
it contains more than a small number of files and directories;
they only need update it when they create, remove or move <samp>.asd</samp> files.
Software distribution managers may also safely create such a cache,
but they must be careful to update it every time they install, update or remove
a software source repository or installation package.
Finally, advanced developers who juggle with a lot of code
in their <code>source-registry</code> may manually manage such a cache,
to allow for faster startup of Lisp programs.
</p>
<p>This persistence cache can help you reduce startup latency.
For instance, on one machine with hundreds of source repositories,
such a cache shaves half a second at the startup
of every <code>#!/usr/bin/cl</code> script using SBCL, more on other implementations;
this makes a notable difference as to
their subjective interactivity and usability.
The speedup will only happen if the implementation-provided ASDF is recent enough
(3.1.3.7 or later); it is not enough for a recent ASDF upgrade to be present,
since the upgrade will itself be found but
after the old version has scanned the directories without heeding such a cache.
To upgrade the implementation-provided ASDF,
see <a href="Replacing-your-implementation_0027s-ASDF.html#Replacing-your-implementation_0027s-ASDF">Replacing your implementation's ASDF</a>.
</p>

<hr>
<div class="header">
<p>
Next: <a href="Configuration-API.html#Configuration-API" accesskey="n" rel="next">Configuration API</a>, Previous: <a href="Search-Algorithm.html#Search-Algorithm" accesskey="p" rel="prev">Search Algorithm</a>, Up: <a href="Controlling-where-ASDF-searches-for-systems.html#Controlling-where-ASDF-searches-for-systems" accesskey="u" rel="up">Controlling where ASDF searches for systems</a> &nbsp; [<a href="index.html#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="Concept-Index.html#Concept-Index" title="Index" rel="index">Index</a>]</p>
</div>



</body>
</html>