HI, And you don't "collect all the dependency's licences for the binary release.” you only need to list licenses of anything that is included in the release. Dependencies that ae not included don’t need to be mentioned. This is described in more detail at the URL Chris provided.
Kind Regards, Justin > On 3 Nov 2023, at 5:46 pm, LinkinStar <[email protected]> wrote: > > Get it. > > Then we will collect all the dependency's licences for the binary release. > > Best, > LinkinStar > > On Fri, Nov 3, 2023 at 2:20 PM Willem Jiang <[email protected]> wrote: > >> Here are some instructions[1] about composing the License and Notice file. >> If we provide the binary release, we must include the License file of >> third-party dependencies. >> >> [1] https://infra.apache.org/licensing-howto.html >> >> >> Willem Jiang >> >> On Thu, Nov 2, 2023 at 5:07 PM LinkinStar <[email protected]> wrote: >>> >>> Hi, >>> >>> We are learning about the process of releasing a binary and have >>> encountered a few problems. 1. If our third-party dependencies don't have >>> the NOTICE, do we just need our own NOTICE when we release a binary? 2. >> I'd >>> like to ask if there are any Golang projects that have released binaries >> in >>> the past that I can learn from. >>> >>> Thanks. Regards >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
