Re: SVN has been replaced by Mercurial for official Euphoria development

new topic     » goto parent     » topic index » view thread      » older message » newer message

This gets complicated fast.

To me, it looks like to have the complete set of information necessary to accurately determine this, we need to have the following:

Date and time of the latest revision made when the build was done.

Date and time of the when the build itself was compiled and linked.

Hg nodeid / SHA sum hash that uniquely identifies the revision across repos.

Local repo local revision number.

Possibly the path of the build dir on the local box that the build was made on and the hostname of that local box, so we can identify the box that did the build.

The sum of all that information will tell us, unambiguously, which binary is older or newer than another binary, even if devs were to share binary builds and get them mixed up.

I hate to ask, but I feel I just gotta. Do we really need to know all this?

jeremy said...
mattlewis said...
DerekParnell said...

With the new rev id, how can one tell if the revision I'm running was built earlier or later than another revision built on the same day?

I asked a similar question. I think it's also worth while to display the rev, even if only for dev builds. These numbers can get out of sync among repos, but they're definitely useful for a developer.

It should be noted here that even displaying rev, it will not tell if one binary is newer than another. This was the same w/SVN as well. You could be working away for three or four days on a revision. If you do not commit during that time, the rev number (in hg or in the old svn) will remain the same. Thus, you do not have any indication from euphoria itself as to which binary may be newer if you have made no commits. To determine that, simply look at the file date w/dir or ls I guess.

Now, one thing where this is different and in favor of hg is that since your repo is local, you may work to a logical step and commit. Your commit is local and will not affect others until you deem your work complete and decide to push. So, one could commit many times during the development of an addition/change/bug fix and thus your rev number would increase.

Jeremy

new topic     » goto parent     » topic index » view thread      » older message » newer message

Search



Quick Links

User menu

Not signed in.

Misc Menu