-
Notifications
You must be signed in to change notification settings - Fork 195
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
Consider decoupling package->directory lookups from $PWD #64
Comments
Issues go stale after 90d of inactivity. Prevent issues from auto-closing with an If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or |
/lifecycle frozen
Can you show a more complete repro case?
…On Sun, Dec 31, 2017 at 2:09 AM, fejta-bot ***@***.***> wrote:
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually
close.
Prevent issues from auto-closing with an /lifecycle frozen comment.
If this issue is safe to close now please do so with /close.
Send feedback to sig-testing, kubernetes/test-infra and/or @fejta.
/lifecycle stale
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#64 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AFVgVH9bm9fx9gr4EboWcdA3aqFHYKJbks5tF11jgaJpZM4ORdSv>
.
|
See Bazel assumes that the build steps it runs are insensitive to the current working directory. For Gengo this isn't true, it expects certain Go packages to be located at particular parts of the filesystem as resolved relative to (I don't have full context any more since this was filed months ago as a side-effect of some other yak hunt) |
/remove-lifecycle stale |
This directly relates to parsing non-GOPATH repos: #144 (comment) |
Will be fixed in v2 (#259) |
Branching discussion from kubernetes/repo-infra#19
Gengo currently assumes that a package
"k8s.io/foo/bar"
can always be found in${PWD}/k8s.io/foo/bar/
, and becomes very unhappy if the generator program is called from a different directory. This makes its use from Bazel rules complicated, and requires Kubernetes BUILD files to use custom logic such asgo_genrule()
instead of Bazel's built-ingenrule()
.The text was updated successfully, but these errors were encountered: