Currently, sources provided via sources: tag in recipes are not cached. This put us in a danger that we might not be able to rebuild a package if its source is removed upstream. We have seen that in past either sources are removed to moved to a different place.
We propose to allow bits to cache such sources for future. Along with TAR files, we can upload such downloaded sources under SOURCES/URL-Hash/filename . This will allow us to reuse these for future rebuilds (e.g. a old packages who's source has been removed and we have to built it for a newer GCC or arch (riscv64))
This should be a trivial change and it will only effect those packages which use sources: instead of source
Currently, sources provided via
sources:tag in recipes are not cached. This put us in a danger that we might not be able to rebuild a package if its source is removed upstream. We have seen that in past either sources are removed to moved to a different place.We propose to allow bits to cache such sources for future. Along with TAR files, we can upload such downloaded sources under
SOURCES/URL-Hash/filename. This will allow us to reuse these for future rebuilds (e.g. a old packages who's source has been removed and we have to built it for a newer GCC or arch (riscv64))This should be a trivial change and it will only effect those packages which use
sources:instead ofsource