I personally think it would be of great help to newcomers to have a containerized development environment to quickly start experimenting. Non-newcomers would also benefit from it by being able to test their changes on different versions of Linux, for example.
I would prepare a set of scripts and Dockerfile’s in a separate repo to start with, and at least add a link to it to Swift’s main ‘README’ via a PR to see what the community has to say. Maybe an extra paragraph in 'system requirements’? On a slightly more technical note, can you elaborate a bit more on why you’d need a docker-compose? If only for volumes to be in a separate container… Maybe I’m missing something. thanks, max > On Dec 18, 2015, at 12:34 PM, swizzlr via swift-dev <swift-dev@swift.org> > wrote: > > Hacking on Swift > > Just as it’s possible to build Swift in a docker container so too is it > possible to actively develop the language in a Linux environment, while still > benefitting from any local affordances you may have. If there is interest > from the core team, I would be happy to contribute a meta-repo of Swift, > submoduleing all the repos and supplying a docker-compose file which would > enable developers to provision a development machine while being able to > mirror local changes over to the machine. Similarly, “preheated” images could > be built which would eliminate the need for a fresh build when first starting > on the project. >
_______________________________________________ swift-dev mailing list swift-dev@swift.org https://lists.swift.org/mailman/listinfo/swift-dev
