Files
docker-cli/components/engine/pkg
Ahmet Alp Balkan bdccc883c1 Support windows style dockerfile paths for build cmd
Currently TestBuildRenamedDockerfile fails since passing
custom dockerfile paths like:

    docker build -f dir/file .

fails on windows because those are unix paths. Instead, on
windows accept windows style paths like:

    docker build -f dir\file .

and convert them to unix style paths using the helper we
have in `pkg/archive` so that daemon can correctly locate
the path in the context.

Signed-off-by: Ahmet Alp Balkan <ahmetalpbalkan@gmail.com>
Upstream-commit: 5ecab9e831c6d39e649430013087a3e2a85fb949
Component: engine
2015-02-24 20:23:53 -08:00
..
2014-10-24 15:11:48 -07:00
2015-02-19 22:21:17 -08:00
2015-02-13 15:50:42 -07:00
2015-02-19 22:21:17 -08:00
2015-02-04 10:47:37 +08:00
2014-12-06 22:52:19 +08:00
2014-10-24 15:03:06 -07:00
2015-01-12 22:47:36 +00:00
2014-10-27 18:59:02 +00:00
2014-11-20 19:33:15 +02:00
2014-03-27 22:44:31 +01:00
2014-07-01 23:44:12 +04:00
2014-11-25 20:49:01 +09:00
2014-11-24 18:10:37 -05:00
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!