On 02/12/2017 08:40 AM, Ben Coman wrote:
On Sun, Feb 12, 2017 at 11:36 PM, Dale Henrichs
<dale.henri...@gemtalksystems.com
<mailto:dale.henri...@gemtalksystems.com>> wrote:
Peter,
<wishful thinking>
In the long term the the MetaRepo should be replaced by a
repository of project specification objects (like this [1]). Each
project specification would contain the meta data for a project
(like this[2]) instead of a copy of a ConfigurationOf that is
almost always out-of-date.
ConfigurationOf should really be phased out -- they've been
obsolete for 3-4 years now... BaselineOf is preferred.
Does BaselineOf work with Monticello?
Technically, yes (bleeding edge), but practically no. That doesn't
change the fact that ConfigurationOf should be phased out ...
There are so many things wrong with the way that ConfigurationOf works:
manual editing required on every package commit, editable version data
that should be immutable, no good branching model, no project-level
version comparison, etc.
5 years ago,I was seriously looking at solving the problems with
ConfigurationOf. I happened to be looking at git for inspiration (mainly
the branching model), but was not really looking forward to the amount
of work that was going to be involved.
Fortunately right about that time Otto Behrens introduced FileTree.
Being able to leverage a fully featured version control system to manage
Smalltalk code in FileTree, meant that instead trying to put effort into
fixing ConfigurationOf, I was able to greatly simplify ConfigurationOf
with BaselineOf ...
Project specification objects would support both ConfigurationOf and
BaselineOf projects ... the current model of only supporting
ConfigurationOf projects with a MetaRepo means that BaselineOf projects
are not really properly supported....
Dale
