Hi! Tomas Volf <[email protected]> skribis:
>> Caching is not documented, it’s an “implementation detail”. There’s no >> way to force the use of the cache (this could be bad since one could >> easily end up caching nonsensical results). > > Details of caching are possibly an implementation detail, but the > caching itself very much is documented: Oh that’s true! We could mention ‘-L’ there. >> The package cache is used to map package specs (name or name+version) to >> variables (like “make” -> (@ (gnu packages base) make)). > > Right, and for specifications->manifest I do follow the logic. But with > packages->manifest I am not doing any such mappings, so I do not > understand why I suffer the penalty from not having the cache. Because if you use ‘-L’ (or ‘GUILE_LOAD_PATH’), we can no longer guarantee that (@ (gnu packages base) hello) corresponds to /gnu/store/2nfg943asrl9dv64zrr1a4kpb25mfafd-hello-2.12.2.drv. Thanks, Ludo’.
