On 5/29/16 5:28 AM, Thierry Goubier wrote:
Le 29/05/2016 14:04, Peter Uhnak a écrit :
On Sun, May 29, 2016 at 11:21:21AM +0200, Thierry Goubier wrote:
Le 29/05/2016 11:15, Peter Uhnák a écrit :
> All this is so that my .5 would not conflict with someone else .5
How is this a problem? Because it will be "Me.5" and "You.5", so there
can't be any conflict.
Me.5 and Me.5 are possible...
Think of numbering your own stuff on two different branches.
More, Metacello depends on Me.5 5 to be greater than You.5 5 for
some of the
baselines / configurations to work properly :)
Can't it use the ancestry to decide?
I suggested that to Dale... Disregard version numbers, only consider
as newer if the other is in the ancestry chain.
For FileTree repos it is even better to just load the package
(Monticello does a good job of only loading the changed packages and
we're looking at packages already on disk) ... ... I have an extension
to Metacello for Filetree repos (it's only been around for about 3
years) that ignores version numbers and "loads" all of the packages from
the the repo (I mentioned _this_ to Thierry:) ... which for FileTree
repos is actually the proper behavior ... I happen to be very busy at
the moment so I don't have time to blow the dust off of that extension
... the big gotcha is everyone has to have the extension present in
their image for this kind of thing to work and AFAIK pharo is not kept
up-to-date with the latest versions that I publish on github, so I'm
afraid that much breakage would ensure if only a few individuals started
using this extension ... Seems to be that we're stuck between a rock and
a had place... I wish there was a better way to keep the Metacello
distribution up-to-date in images that I have no control over ...
FWIW, I've found that if I manually flush the cache for each package
before I save it, I don't have to wait the minute or so for all of the
repos to be refreshed ...
Dale
