[pacman-dev] [PATCH 1/1] support http header to indicate an expected failure

[Andrew Gregory]

On 05/28/21 at 05:55pm, Christian Hesse wrote:
> Allan McRae <allan at archlinux.org> on Fri, 2021/05/28 22:52:
> > >> Does this
> > >> mean the "new" database on the hosts network could be long out of date,
> > >> but as long as it is newer than the local machine being updated, that is
> > >> what will be used?  
> > > 
> > > Well, out-of-date is a term that does barely match here... pacman does
> > > known about the date of its current database files only. So yes, more
> > > recent database files are used as long as they are newer than the local
> > > ones - even if out-of-date compared with a mirror.
> > > 
> > > That's why the pacredir documentation tells you to run `pacman -Sy` twice
> > > to be sure: First run fetches the newest database from local network,
> > > second run (where pacredir returns 404) fetches from mirror if a newer
> > > version is available.  
> > 
> > This does very little to convince me that the CacheServer proposal
> > should be used for databases.
> 
> So let's implement CacheServer for package files only as described
> in FS#23407.
> 
> Apply my patch anyway to make pacman happy with pacredir. :)

-1.  This sounds like exactly the kind of esoteric setup that we keep
the external downloader around for.