Submitted a FileTree bug[1] for this ... I think this is more a function
of FileTree than Metacello ... but I have to uncover the "cypress fix"
and then think about the best place to make the fix ....
Dale
[1] https://github.com/dalehenrich/filetree/issues/166
On 11/9/15 5:27 PM, Dale Henrichs wrote:
On 11/9/15 5:08 PM, Thierry Goubier wrote:
Hi Dale,
I'm back at that again.
And I think that Metacello is already failing with repositories that
have true branches (git + filetree). Metacello delegates to
Monticello which rely on full ordering to establish upgrades or
loading preferences. And on repositories with branches, each branch
has its own ordering, making upgrades a possible problem (such as
switching to a new branch with a new version and discover there that
the top of that branch has a lower version number than the previous
version == no load).
Hmmm ... I can see that this could happen ...
Granted, this is less probable, but could surprise...
I don't like surprises:)
Now, if Metacello could use the semantic versionning present in the
Configurations and Baselines...
Semantic versioning is only used in ConfigurationOf subclasses ... the
notion with git is that the branch should be loaded whether or not it
is an "Monticello package upgrade" or not... I'll have to think on
this one a bit .... I'm in Buenos Aires for Smalltalks this week ...
but I consider this to be somewhat of a major bug, given that folks
are moving more and more to git .... it may be as "simple" as turning
on the "cypress url" for all FileTree repos .... but I want to think
through this one a bit more ...
Dale
