Package: apt Version: 2.1.10 With systems of Continuous Integration becoming widely popular as ever, the `apt-get update` operation is gaining more and more executions. When ran frequently, most of the time, the response would indicate that nothing new is available. And sometimes, when something did update, it's often only a subset of packages from a bigger package list are updated.
The current architecture, as far as I understand it, however, is not suited for minimizing the response time and traffic minimization for these scenarios. What I'd like to ask is, were there considerations to use a more suitable architecture, like using a git repo as an underlying structure to optimise retrieval of updated repository state? Not only is it designed for exactly these use-cases, but it will also add features like being able to see the history of repository's metainfo changes using familiar git tools. In my opinion, it might have a great positive impact. Thank you!
