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 :)
Thierry
Peter
On Sun, May 29, 2016 at 10:37 AM, Sven Van Caekenberghe <s...@stfx.eu
<mailto:s...@stfx.eu>> wrote:
> On 29 May 2016, at 10:28, Holger Freyther <hol...@freyther.de
<mailto:hol...@freyther.de>> wrote:
>
>
>> On 29 May 2016, at 09:58, Sven Van Caekenberghe <s...@stfx.eu
<mailto:s...@stfx.eu>> wrote:
>>
>>
>>>
>>> For some reason the package manager is refreshing all packages. I don't
know why it happens, and it's quite annoying (because it slows down commits), but it
doesn't cause any actual problems, so don't worry about it too much.
>>
>> As I understand it, what happens is the following: before you commit to
your MC repo, you have to find the next version number; a check is then done in all
relevant repos; the cached content is not used, but an actual refresh is done. All
this is so that my .5 would not conflict with someone else .5 - the chance that this
happens is very small, and the check does not really prevent it.
>
> I assumed that but can it be limited to the Repositories that are
associated with the package? I am afraid that next time I travel I can not commit
to my local repository (and ofcourse the speed part). :)
We should go one step further: add an option to totally disable this
check to go outside the target repo, it makes little sense. But MC
is a complex beast ...
> holger
