vbatts/pkg
1
0
Fork 0
Code Pull requests Releases Activity
an [abandoned] attempt to slice out the docker/docker/pkg package
39 commits 2 branches 0 tags 3.9 MiB
Go 100%
Find a file
Guillaume J. Charmes 32bbc76949 Remove all darwin specific files and use more generic _unsupported with build tags. 
Docker-DCO-1.1-Signed-off-by: Guillaume J. Charmes <guillaume.charmes@docker.com> (github: creack)
2014-01-30 23:10:56 +00:00
cgroups execdriver: Make GetPidsForContainer() a driver call 2014-01-28 16:21:49 +01:00
collections Remove std sort and use custom sort for performances 2014-01-26 14:01:38 -08:00
graphdb Move utility package 'graphdb' to pkg/graphdb 2013-12-23 23:33:06 +00:00
iptables network: add publicly mapped ports to FORWARD table 2014-01-28 13:11:49 -06:00
mflag fix mflag import 2014-01-27 23:29:56 +00:00
mount Remove all darwin specific files and use more generic _unsupported with build tags. 2014-01-30 23:10:56 +00:00
namesgenerator Fix misspelled Hawkings -> Hawking, Archimede -> Archimedes, Euclide -> Euclid 2014-01-09 10:02:55 -05:00
netlink Remove all darwin specific files and use more generic _unsupported with build tags. 2014-01-30 23:10:56 +00:00
sysinfo remove ip_forward warning 2014-01-28 13:27:56 -06:00
systemd chore(coreos/go-systemd): copy to github.com/dotcloud/docker/systemd/pkg/activation 2014-01-27 17:18:09 -08:00
term Move utility package 'term' to pkg/term 2013-12-23 23:42:37 +00:00
README.md Add README to pkg 2013-12-23 23:12:19 +00:00

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!