-
Notifications
You must be signed in to change notification settings - Fork 43
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
Plan 9 Support #52
Comments
will be great if you can do a PR |
@henesy I think Go's internal/filelock package does not support Plan 9. |
I'll be sending a PR for Plan 9 support soon. It's not really possible to implement Lock/Unlock using the "exclusive use" bit:
Since Lock is called on an open file, if we can't open a locked file in the first place, we never even get into the Lock function to wait for the file to be unlocked by the other client. I think go-billy will need to use an API similar to the lockedfile package to support file locking on Plan 9. I got all the tests passing on Plan 9, but I found that running |
Fixes src-d#52 Signed-off-by: Fazlul Shahriar <[email protected]>
Fix build on Plan 9 and make all tests pass. Note: running `go test ./...` may hang in `TestTempFileMany` or `TestTempFileManyWithUtil`. I'm not sure if it's a go tool issue, standard library issue, or something wrong with the tests. All tests pass if tests are run with `go test -count 1 ./...`. Fixes src-d#52 Signed-off-by: Fazlul Shahriar <[email protected]>
Fix build on Plan 9 and make all tests pass. Note: running `go test ./...` may hang in `TestTempFileMany` or `TestTempFileManyWithUtil`. I'm not sure if it's a go tool issue, standard library issue, or something wrong with the tests. All tests pass if tests are run with `go test -count 1 ./...`. Fixes src-d#52 Signed-off-by: Fazlul Shahriar <[email protected]>
Getting Billy (osfs) to build on Plan 9 is possible by adding the following:
osfs/os_plan9.go
I changed osfs/os_posix.go's build header to the following, but I'm not sure it's necessary:
// +build !windows,!plan9
The text was updated successfully, but these errors were encountered: