2014-03-16 23:56 GMT+01:00 Sven Van Caekenberghe <[email protected]>: > > On 16 Mar 2014, at 22:44, Nicolas Cellier < > [email protected]> wrote: > > > Or do you have a different POV, like only Pharo3.0 stuff should go to > MetaRepoForPharo3.0, and the ConfigurationOf... should be expunged from any > other dialect/version ? > > MetaRepoForPharo3 should only contain configurations that load/work > without problems in Pharo 3 and that are/will be supported. > > Of course, if a configuration contains supports for other platforms as > well, that is OK. >
Yes, I see that is the current practice. But I mean one could imagine another workflow: - an automated tool extracts pharoX.Y configuration from a multi-dialect configuration This is what is published in MetaRepoForPharoX.Y (maybe a pharoX.Y user don't care that much about squeakZ.T or gemstone nor of a very old version dedicated to Pharo0.1) - the pharoX.Y only configuration is managed via a simple Versionner UI and committed into MetaRepoForPharoX.Y in short cycle until it works well enough - an automated tool merge pharoX.Y configuration back into multi-dialect configuration stored somewhere else I don't think the 1st item is difficult (doesn't Metacello does exactly that when loading) 2nd item is almost what you have currently with Versionner. The 3rd item is the difficult point, it would have to track differences between dialectA and dialectB or dialect version X and dialect version Z, but also consistency of package baselines and versions. However I'm sure automation would be a great improvment in this area (compared to manual dissection of configuration).
