Skip to content
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

Remove dummy mod dir #1121

Merged
merged 21 commits into from
May 3, 2019
Merged

Remove dummy mod dir #1121

merged 21 commits into from
May 3, 2019

Conversation

marpio
Copy link
Member

@marpio marpio commented Mar 11, 2019

From go 1.12 release notes:

When GO111MODULE is set to on, the go command now supports module-aware operations outside of a module directory, provided that those operations do not need to resolve import paths relative to the current directory or explicitly edit the go.mod file. Commands such as go get, go list, and go mod download behave as if in a module with initially-empty requirements. In this mode, go env GOMOD reports the system's null device (/dev/null or NUL).

This means we can remove the dummy mod directory required before by go list and go mod download

@marpio marpio requested a review from a team as a code owner March 11, 2019 20:13
Copy link
Contributor

@marwan-at-work marwan-at-work left a comment

Choose a reason for hiding this comment

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

Unfortunately, there seems to still be issues with that: golang/go#29522

Maybe we should wait until this issue is resolved?

We should definitely have our tests ensure all of this regardless because they pass even after you removed them

@marwan-at-work
Copy link
Contributor

Wow, windows failed but linux didn't :) -- could be the CI/CD set up is not making a clean GOPATH/pkg

@arschles arschles added the do not merge discussion prs, opinion prs, etc. label Apr 9, 2019
@arschles
Copy link
Member

arschles commented Apr 9, 2019

Adding do not merge until golang/go#29522 is resolved

@arschles
Copy link
Member

Now that Athens uses 1.12 to do the downloads, I think we can merge this now, no?

@marpio @marwan-at-work what do you both think?

@marwan-at-work
Copy link
Contributor

marwan-at-work commented Apr 30, 2019

@arschles this would completely break what this PR promises #1201 because nothing would work with 1.11 :)

So I suggest we say that Athens is strictly 1.12+ and merge this PR as long as @marpio is cool w/ it

@arschles
Copy link
Member

Good point RE #1201, I didn't put 2+2 together...

I'm cool with saying 1.12 across the board. @marpio can you fix the azure pipelines build? Looks like there is a version mismatch...

@marpio marpio removed the do not merge discussion prs, opinion prs, etc. label May 2, 2019
@marpio
Copy link
Member Author

marpio commented May 2, 2019

@arschles @marwan-at-work
I think we can merge this if you approve

@marwan-at-work
Copy link
Contributor

@marpio all good on my end as long as we are cool with being 1.12+ and not 1.11+ (go1.13 is soon anyway)

@marpio
Copy link
Member Author

marpio commented May 3, 2019

+1 for 1.12
Are we referring to 1.11 somewhere now that #1201 is in?

Copy link
Contributor

@marwan-at-work marwan-at-work left a comment

Choose a reason for hiding this comment

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

LGTM

@marpio marpio merged commit 8e5b698 into gomods:master May 3, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants