* Mike Gabriel <[email protected]> [251025 13:03]:
Hi Santiago,
On Fr 24 Okt 2025 12:47:20 CEST, Santiago Vila wrote:
* Revisit DEB_BUILD_PROFILES 'noinsttest' and 'nocheck' vs.
DEB_BUILD_OPTIONS
'nocheck': (Closes: #1118264)
- DEB_BUILD_PROFILES='nocheck' -> don't build, don't run and
don't build
the lomiri-content-hub-testability bin:pkg.
Hello. Are you really sure that the above change is correct?
no, I am not 100% sure this is correct.
I believe the spirit of nocheck build profile, in plain English, was
that the "outcome" of building the packages should be the same, and
for that to happen, not only the contents of the packages should be
the same, but also the list of generated packages should also be the
same.
Where does this statement come from? Do we have this written down
somewhere? I get the point of it, but lomiri-content-hub source code
would need adjustments for this to become possible with the effect of
saving CPU time at build time.
Here: https://wiki.debian.org/BuildProfileSpec#Registered_profile_names
nocheck has N + N, so binary packages and their contents cannot
change.
Chris
