[Vm-dev] A proposal to split VMMaker into subpackages WAS: [ VM Maker: VMMaker-dtl.304.mcz ]

David T. Lewis lewis at mail.msen.com
Tue Mar 19 12:19:54 UTC 2013


On Tue, Mar 19, 2013 at 12:51:02PM +0100, Esteban Lorenzano wrote:
> 
> yes... in that case, since some time now I want to propose a VMMaker package split. 
> I still do not have a real suggestion now, but looks to me that we should be able to split it in something like:
> 
> VMMaker-Core
> 	VMMaker-Cog
> 	VMMaker-Interpreter
> 	VMMaker-Plugins
> 		VMMaker-Plugin1
> 		...
> 		VMMaker-PluginN
> VMMaker-InterpreterSimulation
> VMMaker-JITSimulation
> 
> etc...
> 
> (hierarchy for dependences)
> 
> this time we can reduce the granularity and restrain the changes just to where it is needed...
> 
> what do you think?
>

This will be a good idea when, and only when, we have achieved real progress
in merging the oscog and trunk branches. We are not there yet.

I would be interested to hear from Eliot, but from my point of view this would
make it much more difficult to manage the changes between the two branches.

I have some experience in dealing with this in the OSProcess and CommandShell,
and I found that in some cases splitting things into too many packages can
cause a lot of unnecessary work with little real benefit. I would rather live
with the wasted disk space and rely on Monticello to manage the changes.

Clearly though it is a good objective longer term, and we will get there.

Dave
 


More information about the Vm-dev mailing list