impfs_base_docker_image's Introduction

Component	Stability	Note
ubuntu base image	+++++
ubuntu extra packages	+++++	necessary for installing opam/ocaml eg make, git etc
opam	++++	stable, except for big changes eg 1.2.2 -> 2.0
opam package repo	+	changes all the time
ocaml version	+++++	expected to be under our control
opam packages for our libs	+++	fairly stable, providing we accurately specify deps for our packages

Notes

opam package repo changes all the time; makes sense to pick a particular version of this to introduce some stability; but we need to keep reasonably upto date with master
ocaml version: we typically pick a particular reasonably-recent version eg 4.04.x or 4.06.x; as such, this is stable
opam packages for our libs: should be reasonably stable, but when opam package repo is refactored we may discover missing dependencies etc

Plan

work from a local mirror of opam package repo, pinned to some particular commit (reasonably recent)
specify deps for our packages clearly, with comments about why we depend on a particular package; deps should use opam package names, but be aware that these may differ from ocamlfind libs :(

Building imp_fs packages

we typically just build imp_fs (or some public package late in the build)
for core libraries we may have additional dockerfiles

tr61@pc1156:/tmp/l/git/github$ ls -1 */.dockerfile/Dockerfile a_tjr_lib/.dockerfile/Dockerfile c_tjr_btree/.dockerfile/Dockerfile d_tjr_pcache/.dockerfile/Dockerfile <– public, latest in build imp_fs/.dockerfile/Dockerfile impfs_base_docker_image/.dockerfile/Dockerfile

given the above, we expect tjr_lib and btree to be prefixes of pcache
FIXME is there anyway to avoid the replication? we could have a single dockerfile for pcache in this directory, and reference this from tjr_lib etc, which suffices to check tjr_lib build
- but duplication is not really that much provided package dependencies remain stable

Recommend Projects