On Tue, Jun 18, 2013 at 1:01 PM, Esteban Lorenzano <estebanlm@gmail.com> wrote:

well... afaik, no one outside pharo community is using the configurations, the other guys on vm-dev prefer the old way of doing things.�

also, the group "pharo" is intended to include the things necessary to produce a "pharo vm"... this is what time ago was in the ConfigurationOfPharoVM. That means: you can produce a CogVM without loading group "pharo", but not a Pharo VM.�

so so... Because without the compatibility package the configuration does not even load in Pharo, and then you can build air only :).

�

Esteban

On Jun 18, 2013, at 10:26 AM, Guillermo Polito <guillermopolito@gmail.com> wrote:

Hi guys!

I worked yesterday on making VMMaker load and work in Pharo2.0 with filesystem. Now, I want to push my changes in a new development version of ConfigurationOfCog. But I have some questions:

Is ConfigurationOfCog used by other people besides Pharo?

Because so far I see:
�- there are two different groups in the conf: #common and #pharo.

�- In #common, there is CMakeVMMaker (which in turn loads cairo from files.pharo.org :)) and the oscog branch of VMMaker. Both have only as latest committers Igor and Esteban :P. And I�

�- in #pharo there are nativeboost and some compatibility packages.

So there are pharo specific stuff in both groups, or am I mistaken? Should we keep both groups, or make them one and simplify? And how should I push my changes related with filesystem (pharo-specific) then?

Guille