Bug#1069256: debian-policy: clarify requirement for use of Static-Built-Using
- To: Simon Josefsson <simon@josefsson.org>
- Cc: 1069256@bugs.debian.org
- Subject: Bug#1069256: debian-policy: clarify requirement for use of Static-Built-Using
- From: Maytham Alsudany <maytham@debian.org>
- Date: Sun, 02 Mar 2025 13:21:06 +0800
- Message-id: <[🔎] b163cfd83406e7471e9b50f1a1e3f1000d325ba7.camel@debian.org>
- Reply-to: Maytham Alsudany <maytham@debian.org>, 1069256@bugs.debian.org
- In-reply-to: <87h65bqkd0.fsf@josefsson.org>
- References: <a9764a348eb672fbe70b664ceef387da2cde65d6.camel@gmail.com> <3ed0bdc0b32aa43bd32a218464d3b26c09a3963e.camel@gmail.com> <ZsZf-i0CL2u6QadC@thunder.hadrons.org> <a9764a348eb672fbe70b664ceef387da2cde65d6.camel@gmail.com> <d130dab43c5458ab4bbccd8b93072e851217026a.camel__9476.43061387993$1735982670$gmane$org@gmail.com> <87h65bqkd0.fsf@josefsson.org> <a9764a348eb672fbe70b664ceef387da2cde65d6.camel@gmail.com>
Hi Simon,
On Mon, 2025-02-03 at 13:32 +0100, Simon Josefsson wrote:
[...]
> Maybe adding an example for embedded static C object code like this
> would help clarify the intention.
Would adding the following after the first paragraph be sufficient in
your view?
Note that you do not need to list source packages recursively. For example,
consider the following situation: A package named "foo" declares
Static-Built-Using on "bar". "bar" declares Static-Built-Using on "baz". As
long as "foo" does not directly incorporate the contents of the "baz" package
during its build, then "foo" must not list "baz" in its Static-Built-Using
field.
--
Maytham
Attachment:
signature.asc
Description: This is a digitally signed message part
Reply to: