<br><br><div class="gmail_quote">On Fri, Jan 20, 2012 at 1:07 PM, Esteban Lorenzano <span dir="ltr"><<a href="mailto:estebanlm@gmail.com">estebanlm@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Hi,<br>
<br>
ConfigurationOfPharoVM is intended to build pharo distributions of cog vm... packaged with pharo icons, etc.<br>
<br>
Since is a re-packaging and re-branding, it has sense (IMHO) to keep it separated. Squeak guys may want their own, for instance and also Cobalt, Cuis, etc... so I don't consider adequate to pollute ConfigurationOfCog with this branded builds.<br>
</blockquote><div><br>+1 <br>ConfigurationOfCog should be just for loading Cog into an image. For branded VMs -> a separate conf that uses COnfigurationOfCog :)<br><br> </div><blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
Cheers,<br>
Esteban<br>
<br>
El 20/01/2012, a las 7:08a.m., Camillo Bruni escribió:<br>
<div class="HOEnZb"><div class="h5"><br>
><br>
> Why do we have a separate config named ConfigurationOfPharoVM for PharoVMMaker?<br>
><br>
> Unless there are significant changes in PharoVMMaker wouldn't it make sense to rely on the default Configuration and tag the proper releases?<br>
><br>
> best<br>
> cami<br>
<br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>Mariano<br><a href="http://marianopeck.wordpress.com" target="_blank">http://marianopeck.wordpress.com</a><br><br>