> > * keep the ad-hoc scripting to a minimum. So that it's easier to maintain,
> > contribute, and not get too tied to a given tool (e.g. Vagrant)
>
> Absolutely -- it would be really useful to have a reusable set of scripts
> that we could reuse across (e.g.) Docker and Vagrant.
>
See https://github.com/AltGr/opam-user-setup/ for a first prototype
> Thomas Gazagnaire suggest pulling out opam-installext from the Docker scripts
> into an OPAM package so that we can just install it easily.
Excellent idea, too
> > * Now the tough part: setting up the account for a nice default user setup,
> > with a possible choice of editors. For that I'm starting to work on the
> > 'opam package for user setup' (opus ?) ('OCaml TOol Package for User
> > Setup', 'octopus' ? :))
>
> I guess this only applies for whole-VM virtualisation like Vagrant. In the
> case of Docker packages, we can just skip all this and let the host editor
> work. Do we have a page somewhere where we can editor customisation
> instructions easily? Right now it's spread across Real World OCaml's
> installation instructions, the Merlin website, etc.
>
I was hoping it would be as useful for Docker ; on the instructions, yeah, I've
been trying to gather from different sources, and have the hope to attract all
good setups to a single point. I'm still not sure about the relation between
opam-user-setup and the documentation, but the latter needs to be part of the
effort.
> This sounds excellent. What about managing `~/.ocamlinit` as well? That's a
> very common missing step among RWO readers.
Why not indeed.
Cheers,
Louis_______________________________________________
Platform mailing list
[email protected]
http://lists.ocaml.org/listinfo/platform
