Re: git for armv7

bob prohaska <fbsd_at_www.zefox.net> wrote on
Date: Wed, 03 May 2023 18:43:09 UTC :

> On Wed, May 03, 2023 at 10:29:28AM -0700, Mark Millard wrote:
> > 
> > It is still going to be a while before a armv7 git
> > shows up based on the fixed libunwind vintage. The
> > active build of main's latest, when I looked, still
> > predated the libunwind update for when it started.
> > The fix availability for main waits on the next
> > build of main's latest.
> 
> Don't the package servers keep an old package until
> a new one is successfully built to supercede it?

That would work only if each package was independent
of all the others. Otherwise it could be doing things
like mixing an older git package with more recent
package(s) that provide, for example:

/usr/local/lib/libpcre2-8.so.0
/usr/local/lib/libintl.so.8

Such combinations need not be compatible with each
other. So, generally, far more older material
would have needed to be kept around and version
matched with the git download. Everything else
dependent on those 2 libraries would also have
to be dealt with as well. That might involve more
libraries and more programs. Such handling is
a mess and is resource intensive. It is not done.

The old git package stuck around until the
distribution of the packages from the first
failure to build libunwind made it to the
download servers.

These sort of things happen less with quarterly,
which is part of why some folks use quarterly:
Less frequent subsetting of of their desired
combination of packages.


===
Mark Millard
marklmi at yahoo.com