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
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.
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
On Fri, Jan 20, 2012 at 1:07 PM, Esteban Lorenzano estebanlm@gmail.comwrote:
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.
+1 ConfigurationOfCog should be just for loading Cog into an image. For branded VMs -> a separate conf that uses COnfigurationOfCog :)
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
On 20 January 2012 13:07, Esteban Lorenzano estebanlm@gmail.com 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?
is it branch of VMMaker? 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.
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
El 20/01/2012, a las 11:42a.m., Igor Stasenko escribió:
On 20 January 2012 13:07, Esteban Lorenzano estebanlm@gmail.com 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.
On 20 January 2012 16:01, Esteban Lorenzano estebanlm@gmail.com wrote:
El 20/01/2012, a las 11:42a.m., Igor Stasenko escribió:
On 20 January 2012 13:07, Esteban Lorenzano estebanlm@gmail.com 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.)
ah... phew.. i feared the worst naming is confusing :) nevermind then. you did the right thing
vm-dev@lists.squeakfoundation.org
-
Camillo Bruni -
Esteban Lorenzano -
Igor Stasenko -
Mariano Martinez Peck