an [abandoned] attempt to slice out the docker/docker/pkg package
Find a file
Michael Crosby 43a219048a Merge branch 'add-netlink-functions' of github.com:crosbymichael/docker into add-netlink-functions
Docker-DCO-1.1-Signed-off-by: Michael Crosby <michael@crosbymichael.com> (github: crosbymichael)
2014-02-11 03:33:18 -08: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 Update/fix build tags, Dockerfile, and release.sh for proper building and releasing of linux/386 and linux/arm cross-compiled client binaries 2014-01-31 03:16:42 -07:00
iptables iptables: use dest_addr and dest_port for public port FORWARD rule 2014-02-04 11:32:50 -06:00
mflag fix panic in mflag 2014-01-31 11:39:29 -08:00
mount Merge pull request #3841 from alexlarsson/separate-base-fs 2014-01-31 11:49:14 -08:00
namesgenerator Fix misspelled Hawkings -> Hawking, Archimede -> Archimedes, Euclide -> Euclid 2014-01-09 10:02:55 -05:00
netlink Merge branch 'add-netlink-functions' of github.com:crosbymichael/docker into add-netlink-functions 2014-02-11 03:33:18 -08:00
sysinfo remove ip_forward warning 2014-01-28 13:27:56 -06:00
systemd pkg: systemd: add initial MAINTAINERS 2014-02-06 12:04:35 -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

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!