mirror of
https://gitlab.com/pulsechaincom/go-pulse.git
synced 2024-12-25 12:57:17 +00:00
289b30715d
This commit converts the dependency management from Godeps to the vendor folder, also switching the tool from godep to trash. Since the upstream tool lacks a few features proposed via a few PRs, until those PRs are merged in (if), use github.com/karalabe/trash. You can update dependencies via trash --update. All dependencies have been updated to their latest version. Parts of the build system are reworked to drop old notions of Godeps and invocation of the go vet command so that it doesn't run against the vendor folder, as that will just blow up during vetting. The conversion drops OpenCL (and hence GPU mining support) from ethash and our codebase. The short reasoning is that there's noone to maintain and having opencl libs in our deps messes up builds as go install ./... tries to build them, failing with unsatisfied link errors for the C OpenCL deps. golang.org/x/net/context is not vendored in. We expect it to be fetched by the user (i.e. using go get). To keep ci.go builds reproducible the package is "vendored" in build/_vendor.
41 lines
1.9 KiB
Go
41 lines
1.9 KiB
Go
// Copyright (c) 2014-2015 The Notify Authors. All rights reserved.
|
|
// Use of this source code is governed by the MIT license that can be
|
|
// found in the LICENSE file.
|
|
|
|
// Package notify implements access to filesystem events.
|
|
//
|
|
// Notify is a high-level abstraction over filesystem watchers like inotify,
|
|
// kqueue, FSEvents, FEN or ReadDirectoryChangesW. Watcher implementations are
|
|
// split into two groups: ones that natively support recursive notifications
|
|
// (FSEvents and ReadDirectoryChangesW) and ones that do not (inotify, kqueue, FEN).
|
|
// For more details see watcher and recursiveWatcher interfaces in watcher.go
|
|
// source file.
|
|
//
|
|
// On top of filesystem watchers notify maintains a watchpoint tree, which provides
|
|
// strategy for creating and closing filesystem watches and dispatching filesystem
|
|
// events to user channels.
|
|
//
|
|
// An event set is just an event list joint using bitwise OR operator
|
|
// into a single event value.
|
|
//
|
|
// A filesystem watch or just a watch is platform-specific entity which represents
|
|
// a single path registered for notifications for specific event set. Setting a watch
|
|
// means using platform-specific API calls for creating / initializing said watch.
|
|
// For each watcher the API call is:
|
|
//
|
|
// - FSEvents: FSEventStreamCreate
|
|
// - inotify: notify_add_watch
|
|
// - kqueue: kevent
|
|
// - ReadDirectoryChangesW: CreateFile+ReadDirectoryChangesW
|
|
// - FEN: port_get
|
|
//
|
|
// To rewatch means to either shrink or expand an event set that was previously
|
|
// registered during watch operation for particular filesystem watch.
|
|
//
|
|
// A watchpoint is a list of user channel and event set pairs for particular
|
|
// path (watchpoint tree's node). A single watchpoint can contain multiple
|
|
// different user channels registered to listen for one or more events. A single
|
|
// user channel can be registered in one or more watchpoints, recurisve and
|
|
// non-recursive ones as well.
|
|
package notify
|