This is an automated email from the git hooks/post-receive script. guillem pushed a commit to branch main in repository dpkg.
View the commit online: https://git.dpkg.org/cgit/dpkg/dpkg.git/commit/?id=7c2eb2043a889e07f7d76d842048077f7539fd15 commit 7c2eb2043a889e07f7d76d842048077f7539fd15 Author: Guillem Jover <[email protected]> AuthorDate: Fri Mar 25 22:11:54 2022 +0100 man: Clarify uses cases for Static-Built-Using Mention explicitly some of the use cases this field was thought for, instead of letting it be the vague "static building", which can give room to think it only applies to static linking. Where the intention was for any type of static building, including also source-centered language builds (like with Go or Rust), inclusion of header-only libraries from C/C++, data blobs injection into code, etc. Prompted-by: Shengjing Zhu <[email protected]> --- man/deb-control.pod | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/man/deb-control.pod b/man/deb-control.pod index 186178fd4..9f1de6a21 100644 --- a/man/deb-control.pod +++ b/man/deb-control.pod @@ -391,7 +391,10 @@ within the archive. =item B<Static-Built-Using:> I<package-list> This dependency field lists extra source packages that were used during the -build of this binary package, for static building purposes. +build of this binary package, for static building purposes (for example +linking against static libraries, builds for source-centered languages such +as Go or Rust, usage of header-only C/C++ libraries, injecting data blobs +into code, etc.). This is useful to track whether this package might need to be rebuilt when source packages listed here have been updated, for example due to security updates. -- Dpkg.Org's dpkg
