Re: git for armv7

On Wed, May 03, 2023 at 08:16:01PM -0700, Mark Millard wrote:
> 
> I gather you are not building your own ports for
> this context.

I certainly didn't build the initial installation of git
for this host. IIRC, the sequence was 

Set up disk
install git via pkg from public repository
clone /usr/src and eventually /usr/ports
track -current for a while, successfully
set up poudriere, using your instructions
build a few ports, one by one, successfully
creats pkg/repos/custom.conf and dis-enable pkg/repos/FreeBSD.conf
Check that pkg searched only the local repo; it did
try to build git, which failed in libunwind
try to update sources, but git seemed gone, including man pages

I cannot exclude the possibility of an inadvertent pkg delete,
but certainly didn't do it intentionally.

Essentially I'm trying to use poudriere instead of manual
make in the ports tree to maintain the tiny handful of ports
needed for the host. I only tried it because poudriere is
now useabe thanks to your instructions and fails less often
than make. On a Pi2 it seems a big hammer applied to a small 
nail.

The few simple ports I use (mutt, tin, apache24, bind) 
don't generally require poudriere to compile successfully, 
but once set up it works reliably if slowly. Given a shift 
to 0.5-1.0 TB hard drives instead of microSD, space isn't a 
concern as it was before. 

Perhaps my habit of building ports via poudriere one at
a time contributes to this or future problems. The man
pages mostly emphasize synchronized updates of all ports,
not piecemeal installs and updates. I thought that was
geared to administrator efficiency, but maybe package
consistency is an issue as well. For my part, rebuilding
all installed ports to add or update one feels like
looking for trouble. Maybe not.

Thanks for reading, and all your help!

bob prohaska