Hi all, > Put in the Hg rev-nr in the fourth element instead of the SVN rev-nr > and it will work well for all packages generated from the same repo. > If the repo is a fresh clone of the SF central repo, the likelihood is > very high that .1234 will stay .1234 across different packagers - > important for distribution / package managing software. On the other > hand, if you've played with the repo (e.g. you're a developer), then > your .1234 will be different than mine .2345 - not a problem if these > packages are only part of the dev process and not distributed.
I don't agree. That will create more confusion for developer. When there is a bug report I have to know from which version it is reported. When each builder uses her own numbering sheme it is not helpful, because I as a developer don't know from which point the bug report comes (or if it is fixed in an following revision). A possible solution would be that the builder have to provide in this case a mapping of there repo number to the changeset so that I can check in my repo (with other rev number) if this bug is still appliable or if it is fixed by an already done bug fixing. But this is complicated. I'm for using the changeset sha1 number as Harry already done. With a small modification it should be possible to copy the version string from the about screen. Thomas -- You received this message because you are subscribed to the Google Groups "hugin and other free panoramic software" group. A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/hugin-ptx
