Skip to content

Conversation

bkcsoft
Copy link
Member

@bkcsoft bkcsoft commented Apr 12, 2017

See title

@tboerger I think you have to create the .sig-file for Drone

@bkcsoft bkcsoft added type/docs This PR mainly updates/creates documentation topic/code-linting labels Apr 12, 2017
@bkcsoft bkcsoft requested review from tboerger and metalmatze April 12, 2017 16:58
rm -f NOTICE # `govendor license` appends...
govendor license -o NOTICE +v

notice-up-to-date: NOTICE
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Since it is a test maybe prepend it name with test- ? and add .PHONY just in case ?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe we could even used a more generic name like test-generate-diff and include generation of NOTICE in make generate or in go generate ?

@tboerger
Copy link
Member

I don't think that it makes sense to list all license files in detail. Beside that it's not properly formatted. A listing of the used licenses? Ok... But every license? Wtf?

@tboerger tboerger added the lgtm/need 2 This PR needs two approvals by maintainers to be considered for merging. label Apr 15, 2017
@bkcsoft
Copy link
Member Author

bkcsoft commented Apr 15, 2017

@tboerger It lists all vendored licenses. Anything that isn't vendored shouldn't be in use and vice versa :)

@bkcsoft
Copy link
Member Author

bkcsoft commented Jun 15, 2017

@tboerger This is standard practice for larger projects though :/

@bkcsoft bkcsoft force-pushed the bkcsoft/makefile-notice branch from 77ae57d to 370e329 Compare June 15, 2017 05:53
@strk
Copy link
Member

strk commented Jul 13, 2017

Why adding the NOTICE file at all if it can be generated from vendor/ directory ?

@bkcsoft bkcsoft closed this Jul 18, 2017
@bkcsoft bkcsoft deleted the bkcsoft/makefile-notice branch July 18, 2017 19:53
@go-gitea go-gitea locked and limited conversation to collaborators Nov 23, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
lgtm/need 2 This PR needs two approvals by maintainers to be considered for merging. topic/code-linting type/docs This PR mainly updates/creates documentation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants