moby--moby/pkg
Aleksa Sarai ee99b5f2e9 pkg: remove unused filenotify
pkg/filenotify isn't used anymore and it causes problems with
hack/vendor.sh (nothing uses it, so hack/vendor.sh will remove the
vendored code).

Signed-off-by: Aleksa Sarai <asarai@suse.com>
2016-02-18 00:11:43 +11:00
..
aaparser apparmor: fix version checks to work properly 2016-02-15 20:36:07 +11:00
archive Windows CI: test-unit pkg\archive step 1 2016-02-12 10:13:44 -08:00
authorization Windows CI: test-unit turn off pkg\authorisation 2016-02-11 17:42:12 -08:00
broadcaster
chrootarchive
devicemapper
directory
discovery
fileutils
gitutils
graphdb
homedir
httputils
idtools
integration Windows CI: Fix test-unit for pkg\integration 2016-02-11 15:06:22 -08:00
ioutils Cleanup WriteFlusher 2016-02-09 14:02:26 -05:00
jsonlog
jsonmessage
locker
longpath
loopback
mflag
mount Windows CI: Unit Test - pkg/mount is Unix specific 2016-02-10 18:09:15 -08:00
namesgenerator
parsers
pidfile
platform
plugins Add support for forwarding Docker client through SOCKS proxy 2016-02-16 11:09:28 -08:00
pools
progress
promise
proxy
pubsub optimize pubsub.Publish function 2016-02-15 19:25:21 +08:00
random
reexec
registrar
signal
stdcopy
streamformatter
stringid
stringutils
symlink
sysinfo
system
tailfile
tarsum fix common misspell 2016-02-11 15:49:36 -08:00
term
tlsconfig
truncindex
urlutil
useragent
version
README.md

README.md

pkg/ is a collection of utility packages used by the Docker project without being specific to its internals.

Utility packages are kept separate from the docker core codebase to keep it as small and concise as possible. If some utilities grow larger and their APIs stabilize, they may be moved to their own repository under the Docker organization, to facilitate re-use by other projects. However that is not the priority.

The directory pkg is named after the same directory in the camlistore project. Since Brad is a core Go maintainer, we thought it made sense to copy his methods for organizing Go code :) Thanks Brad!

Because utility packages are small and neatly separated from the rest of the codebase, they are a good place to start for aspiring maintainers and contributors. Get in touch if you want to help maintain them!