-
Notifications
You must be signed in to change notification settings - Fork 365
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
Help fix go.mod mess #246
Comments
for context I think Go modules expect that v2 and higher are referenced with a version in the import path (github.com/go-ldap/ldap/v3 or something) in this case. (#241 was on the right track I think, but I prematurely closed it) |
#241 was merged and I think this fixes things. I had to do a |
I think #241 was along the right lines, however it should have been moved into a v3 subdirectory (or branch) To prevent any real breaking changes, they also suggest that we increment the version to v4. It falls out of line LDAPv3 but could prevent any further breaking changes caused by this and asn1-ber.v1 |
I think this is resolved. |
@johnweldon I'm still having
Here I am trying to build a project that depends on this one:
This is driving me crazy as it's the only LDAP library that is working for me so far. I'm not sure how I ever got it working though....Maybe by not using modules? Even that approach no longer works. Edited to add: I can build my code if I use GOPATH and do |
Try importing |
It works! Thanks. |
I spent some time staring at the following error messages (I was flailing around and no longer remember how they were produced exactly):
If you're seeing these, make sure your application code is explicitly importing |
Help wanted to try fix the go.mod mess for this library.
Issues #238, #240, #242 and related pull requests were an attempt to get the ldap library working as a go module.
It doesn't appear to have worked correctly, and I don't have a lot of time to fix this.
Any help from a go modules veteran would be appreciated!
The text was updated successfully, but these errors were encountered: