Last week I noticed the same behavior... not really such a big fan of it On 2012-01-29, at 20:05, Sven Van Caekenberghe wrote:
Today I pressed Command-. while looking at a slow Monticello save, I was wondering what the system was doing before I even had written my commit message.
Apparently, MCWorkingCopy>>#uniqueVersionName checks every repository linked to the package, (6 for Zn in my case), to see if the proposed version name is unique across all these repositories, not using the cache.
I understand this, but this comes down to 6 times getting the list of all package names from remote servers.
One way to speed this up would be to parallelize these.
I guess that could be done with very little effort.
But fundamentally, I thought Monticello was supposed to be a distributed version control system ?
Would it not be possible to assign the version name based on local, best effort knowledge alone and deal with possible conflicts afterwards (there is the ancestory) ?
to me that would make more sense. - Is it necessary that the version name is globally unique? I doubt so. - Having it unique per repository should be enough, no?
Just thinking out loud.
Sven