diff options
| author | Angelos Evripiotis <jevripiotis@bloomberg.net> | 2019-02-20 10:22:32 +0000 |
|---|---|---|
| committer | Angelos Evripiotis <jevripiotis@bloomberg.net> | 2019-02-20 14:07:24 +0000 |
| commit | 9382001c5f69117ae462e913356ef27d4d9a902f (patch) | |
| tree | 6478143a06a19254f21dbef0d448f28e5dc15a60 | |
| parent | 53f94d055890b4d2008e31be9b77a7cdb34e8aa3 (diff) | |
| download | buildstream-9382001c5f69117ae462e913356ef27d4d9a902f.tar.gz | |
doc/./arch_cachekeys: note no direct runtime deps
I was mistaken on this point in my first reading. The sentence on strong
and weak key equivalency made me check my assumptions.
Help others with the same misunderstanding by explicitly calling this
out in a new paragraph.
| -rw-r--r-- | doc/source/arch_cachekeys.rst | 3 |
1 files changed, 3 insertions, 0 deletions
diff --git a/doc/source/arch_cachekeys.rst b/doc/source/arch_cachekeys.rst index 8e74a37f9..0d469de4b 100644 --- a/doc/source/arch_cachekeys.rst +++ b/doc/source/arch_cachekeys.rst @@ -42,6 +42,9 @@ or the environment changes but it will not change when a dependency is updated. For elements without build dependencies the ``strong`` cache key is identical to the ``weak`` cache key. +Note that dependencies which are not required at build time do not affect +either kind of key. + Strict build plan ----------------- This is the default build plan that exclusively uses ``strong`` cache keys |