Ephestos is my project that is a single configuration that unites all my other projects under one roof. Ephestos loads 1) Nireas 2) ChronosManager 3) SmaCC (not mine) 4) Atlas 5) CPP 6) Octopus 7) BPY 8) Orpheas . Each one of them a separate git repo with its own baseline. Some of them depend on each other. Also each of those repos has its own configuration in case I want to install it separately. So this way I can build my own image with a single click. https://github.com/kilon/Ephestos/blob/master/BaselineOfEphestos.package/BaselineOfEphestos.class/instance/baseline..st
So yeah I would like for Package Browser to stay, it works great for me and I have not even used the convenience of git tags, branches, github releases and git modules yet that would easily allow me to build insanely complex images with a single click. On Mon, 17 Apr 2017 at 00:25, Stephan Eggermont <step...@stack.nl> wrote: > On 16/04/17 16:14, Dimitris Chloupis wrote: > > Just for the record the easiest way to load packages in the image the > > Package Browser relies solely on configurations . Is there a plan to > > migrate because as much I am vocal supporter of Pharo moving to git it > > will be a big lose if Package Browser is not ported . > > Which browser do you mean? Catalog? That generally does not work well > because it cannot deal with combinations of configurations. > > Stephan > > > >
