I'd like to redistribute bazelisk binaries along with my own software, to help my users with bootstrapping.
Without digging into the bazelisk build dependencies in detail, it's difficult for me to figure out what notices should accompany the binaries, because https://github.com/bazelbuild/bazelisk/releases does not appear to have any notices posted.
Is there a way that the bazelisk binary releases could provide the aggregated notices of all of the works it derives from, so that I could simply propagate that along with the binary, when I redistribute it? (Maybe a zipfile of the notices on the releases page?) Or maybe a "bazelisk bazelisk-notices" command could dump the text at runtime? I'm open to any kind of solution, really -- I just want to avoid the need to scrape it together on my own when I upgrade bazelisk.
I'd like to redistribute
bazelisk
binaries along with my own software, to help my users with bootstrapping.Without digging into the
bazelisk
build dependencies in detail, it's difficult for me to figure out what notices should accompany the binaries, because https://github.com/bazelbuild/bazelisk/releases does not appear to have any notices posted.Of course, I see https://github.com/bazelbuild/bazelisk/blob/master/LICENSE which I can ship alongside the binary. However, it seems like there might also be additional notices that I should be incorporating, such as https://github.com/mitchellh/go-homedir/blob/master/LICENSE or https://github.com/hashicorp/go-version/blob/master/LICENSE or etc.
Is there a way that the
bazelisk
binary releases could provide the aggregated notices of all of the works it derives from, so that I could simply propagate that along with the binary, when I redistribute it? (Maybe a zipfile of the notices on the releases page?) Or maybe a "bazelisk bazelisk-notices" command could dump the text at runtime? I'm open to any kind of solution, really -- I just want to avoid the need to scrape it together on my own when I upgrade bazelisk.