El 20/01/2012, a las 11:42a.m., Igor Stasenko escribió:
>
> On 20 January 2012 13:07, Esteban Lorenzano <
[hidden email]> wrote:
>>
>> Hi,
>>
>> ConfigurationOfPharoVM is intended to build pharo distributions of cog vm... packaged with pharo icons, etc.
>>
>> 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.
>>
> yes, but you missed second question:
> why it uses PharoVMMaker?
PharoVMMaker is for CMakeVMMaker configs... there is no a PharoVMMaker
>
> is it branch of VMMaker?
no
> My thoughts on it, that instead of making branch (with which you will
> need to merge all the time), create an extra package with patches you
> need for Pharo VM, and load it after "vanilla" VMMaker package.
> Because if we will have so many branches it will be really hard to
> keep them all up to date.
we are not making a branch, just a CMakeVMMaker config for pharo branding (or for squeak, etc.)
>
>> Cheers,
>> Esteban
>>
>> El 20/01/2012, a las 7:08a.m., Camillo Bruni escribió:
>>
>>>
>>> Why do we have a separate config named ConfigurationOfPharoVM for PharoVMMaker?
>>>
>>> Unless there are significant changes in PharoVMMaker wouldn't it make sense to rely on the default Configuration and tag the proper releases?
>>>
>>> best
>>> cami
>>
>
>
>
> --
> Best regards,
> Igor Stasenko.
Locked
