Re: git for armv7

On 04/05/2023 04:32, bob prohaska wrote:
> On Wed, May 03, 2023 at 12:38:58PM -0700, Mark Millard wrote:
>> bob prohaska <fbsd_at_www.zefox.net> wrote on
>> Date: Wed, 03 May 2023 18:43:09 UTC :

[..]

>> 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.
> 
> Ahh, that makes sense. Old packages have too
> much baggage 8-) for the public servers.
> 
> What happens in the case of a local poudriere
> repository? If it once builds a package, which
> subseqently fails, is the successful build
> deleted?

I would like to recommend some settings for local builds in poudriere.conf
ATOMIC_PACKAGE_REPOSITORY=yes
COMMIT_PACKAGES_ON_FAILURE=no

These are very useful if you want a working repository for your machines 
every time you run "pkg install" or "pkg upgrade". Nothing is more 
frustrating than trying to build an update in Poudriere and it fails, 
leaving you with a broken repository. That's why we use atomic yes and 
don't commit on failure.
It changes slightly what Mark Millard described - Poudriere does not 
remove packages from your repository before building. It does it on a 
separate copy of the repository that is only used for the bulk build, 
and if it fails, your real repository remains untouched.

If you want to keep older repositories, you can set the following 
variables (we keep 3)

KEEP_OLD_PACKAGES=yes
KEEP_OLD_PACKAGES_COUNT=3

Kind regards
Miroslav Lachman