Since we have a very capable CDN infrastructure, it is possible for us to implement a 'closed loop' distfiles infrastructure which leverages the CDN for all our distfiles.
This is a tighter integration and will resolve issues with upstream sources being changed underneath us, and will ensure that the distfile we are expecting is the one that is available to users. Currently, an ebuild will make an effort to retrieve from our CDN but the distfile is not guaranteed to be there. At least for autogens, it is possible for metatools to ensure that the expected distfile binary data is available and matches what is expected by the ebuild.
This can potentially also reduce some of the complexity in some autogens where this is an ongoing problem, and would be a very good capability to offer in metatools in general.
- relates to
-
FL-9647 Eliminate digest failures from funtoo CDN distfiles
- Closed