-
Notifications
You must be signed in to change notification settings - Fork 4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Docs do not mention third_party requirements for a license #642
Comments
To work around this, you can add a |
Is this restriction going to be relaxed? It seems a bit inconsistent to enforce this for |
Yes AFAICT it should be relaxed and replaced by the constraint mechanism. On Fri, Nov 27, 2015, 8:52 PM Kamal Marhubi notifications@github.com
|
+1. I ran into this today and was not able to find any documentation about which licenses are available or what the license() command does. |
Here is the documentation on |
I added some documentation here: https://github.com/bazelbuild/bazel/blob/master/src/main/java/com/google/devtools/build/lib/packages/PackageFactory.java#L722-L741, which I incorrectly thought would be included in the generated docs. We should move it somewhere else so it will show up in the documentation. |
Eventually... it needs to be moved to a different file. |
The existing documentation describes what, but not why. From some digging, it appears that |
I added a directory in my toplevel called third_party, and when building a rule within it I got an error:
Searching for third_party in the bazel docs does not turn up anything about this restriction: http://bazel.io/search.html?q=third_party
The text was updated successfully, but these errors were encountered: