Bug#1069256: debian-policy: clarify requirement for use of Static-Built-Using

[Julian Gilbey <jdg@debian.org>]

On Sat, Aug 16, 2025 at 07:42:32PM +0200, Guillem Jover wrote:
> Hi!
> [...]
> I guess my concern with at least turning this into a "should" is that
> it feels it would potential imply a burden to whoever might be on the
> receiving end of this, where I don't think we are currently ready to
> honor that commitment (due to missing tooling, processes, etc).
> 
> I think the rest of the clarification looks good, and I'd have no
> problem with incorporating that in into the man page, let's say
> perhaps for now with this?
> 
>   This is useful to track whether this package might need to be
>   rebuilt when source packages listed here have been updated, for
>   example because of changed functionality potentially impacting
>   the package behavior, or for security updates.
> 
> And we can apply the "should" part later on, once/if we are ready
> to handle that.

This sounds like a very reasonable, non-committal description.  Nice
wording!  The only change I'd make is "source packages" -> "packages",
as we're suggesting recording the binary package used in the build,
not the source package.  So the resulting paragraph would read:

  This is useful to track whether this package might need to be
  rebuilt when packages listed here have been updated, for
  example because of changed functionality potentially impacting
  the package behavior, or for security updates.

Best wishes,

   Julian