2016-10-28 14:12 GMT+02:00 Guille Polito <guillermopol...@gmail.com>:
> But the functionality is there, it's just that it is not loaded by default. > > Loading it by default implies wedding Pharo's life cycle with > OS(Sub)Process' one, and having to maintain the possibility of dependencies > to OS(Sub)Process spreading in the entire environment. > Like many of the other projects loaded by default in a Pharo image. What is wrong with OSSubprocess or OSProcess so that they can't be treated the same? > > What is wrong in executing a simple Metacello command to load it? > The fact the image doesn't come as a one download / ready to use for an average user? Thierry > > > -------- Original Message -------- > > I have a love and hate relationship with Pharo > this one I will put in the hate category > > You expect people to use pharo when you do not offer functionality they > come to expect from the language they already use and not even offer an > altervative, say a library with similar command line functionality (See > Scale). > > On Fri, Oct 28, 2016 at 2:59 PM Norbert Hartl <norb...@hartl.name> wrote: > >> >> > Am 28.10.2016 um 13:17 schrieb Dimitris Chloupis <kilon.al...@gmail.com >> >: >> > >> > I just noticed that OSProcess misses from Pharo 6 image, it was >> supposed to be replaced by OSSubProcess but this not in the image either ? >> What we suppose to use to execute bash from inside pharo ? >> >> It was never in the image. You need to install it in order to use it. >> >> Norbert >> >> >> >
