Sources in Bottlerocket are content-addressed and stored in a "lookaside cache," which is used during the build to fetch source artifacts.
Currently buildsys assumes a singular lookaside cache. While this could be overridden, it would be cumbersome to maintain a workspace that wished to use multiple lookaside caches for package sources. (For example, consider a kit that wished to rebuild sources from core-kit with different options.)
One possible solution is to allow Twoliter.toml to support being configured with a series of lookaside caches that it checks for artifacts sequentially.
Sources in Bottlerocket are content-addressed and stored in a "lookaside cache," which is used during the build to fetch source artifacts.
Currently
buildsys
assumes a singular lookaside cache. While this could be overridden, it would be cumbersome to maintain a workspace that wished to use multiple lookaside caches for package sources. (For example, consider a kit that wished to rebuild sources fromcore-kit
with different options.)One possible solution is to allow Twoliter.toml to support being configured with a series of lookaside caches that it checks for artifacts sequentially.