Re: [PATCHv8] nss_db: protect against empty mappings

[DJ Delorie <dj at redhat dot com>]

"Carlos O'Donell" <carlos@redhat.com> writes:
> I wonder if we can't make the workflow different, an this is purely
> a psychological thing:
>
> (a) Make a "build done" stamp.

What build?  What targets?  There are a lot of installable bits in the
testroot that can be built independently.  Without a fully
dependency-driven install, it's very hard to detect that "something
changed" which would require a re-install.

Of course, we could check for libc.so itself being newer than
install.stamp, and maybe libm.so if it had containerized tests.

> (b) Compare "build done" stamp with "chroot stamp" and if they are

I suspect this could be centralized into the support routines that
handle exit codes; looking at "/install.stamp" and some other file.
Aside from the problem of reliably creating the "some other file", which
would have to be inside the container also.