OK, Thanks for the reply. So, If we just use them, we don't need to put anything on NOTICE about dependencies, right? How about the license? Does the licence need to include third-party dependencies in the zip containing the binary in the release? For example, like this https://github.com/apache/linkis/blob/master/linkis-dist/release-docs/LICENSE
I am not sure and just want to find an example. Best, LinkinStar On Thu, Nov 2, 2023 at 5:14 PM Christofer Dutz <[email protected]> wrote: > Well, > > we don’t release the third-party dependencies, so we theoretically just > use them, if the licensing is compatible. > > If we copy code from third-party projects, we need to keep the license > headers intact and need to list which files were copied from which project > and which license they were under in our NOTICE files. > > I hope that was correct (Wave in the direction of Justin) ;-) > > Chris > > Von: LinkinStar <[email protected]> > Datum: Donnerstag, 2. November 2023 um 10:06 > An: [email protected] <[email protected]> > Betreff: About the process of releasing a binary > 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 >
