Skip to content

Conversation

mickvandijke
Copy link
Member

@mickvandijke mickvandijke commented Aug 31, 2022

@mickvandijke
Copy link
Member Author

Hey @da2ce7 ,

I have made a workflow that automatically releases compiled binaries of the index-backend when the main branch is updated.

I am however wondering if we have to include a license notice with every binary? And if so, do we have to do the same thing for every crate in the Cargo.toml?

@mickvandijke mickvandijke requested a review from da2ce7 August 31, 2022 16:41
@da2ce7
Copy link
Contributor

da2ce7 commented Aug 31, 2022

@WarmBeer I think that it is good to include the LICENCE file in the packages as a general rule.

I don't know if it required by the license to include the license, I suspect for AGPL it is required to also include a copy of it. - However I don't think that this requirement is so important. We could make this exception official by adding a the line to our license.

"We make the exception that projects that distribute this work only need to include the name and version of the license, instead of needing to include them verbatim in the package".

@da2ce7 da2ce7 requested a review from josecelano August 31, 2022 17:38
@mickvandijke mickvandijke merged commit 837e4ec into main Sep 12, 2022
@mickvandijke mickvandijke deleted the workflow-59-auto-add-compiled-binaries-for-macos-linux-and-win64-on-release branch September 12, 2022 13:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

2 participants