On Mar 27, 2016 6:24 PM, "Chris Johns" <chr...@ntpsec.org> wrote: > > On 26/03/2016 8:05 AM, Amar Takhar wrote: >> >> On 2016-03-25 13:51 -0700, Hal Murray wrote: >>>> >>>> So, ntpd 0.9.2-afceec0+ >>> >>> >>> I'd put the + right after the 2: >>> ntpd 0.9.2+afceec0 or ntpd 0.9.2+ if you build without git. >>> >>> My normal mode of operation is to have a master copy on one system, rsync to >>> other systems dropping the .git directory to save space and time, and then >>> build there. >>> >>> (.git is 75% of the space) >> >> >> I will put the + there if it is not in release mode. This will ensure the + >> stays even when you rsync devel w/out the .git directory. >> > > On other projects I have started to add 'modified' or 'm' with the git hash to indicate the git repo being built has local modifications.
I was also thinking that leaving the development version with the same base version as the last release doesn't help people doing anything conditional on the version. V0.9.2+ is really V0.9.3-. It is more than the last release and may have incompatibilities or enhancements that you need to know about. That's true of libraries and things like gcc. Not sure for NTPsec if external users need that probe to mean something --joel > Chris > > _______________________________________________ > devel mailing list > devel@ntpsec.org > http://lists.ntpsec.org/mailman/listinfo/devel
_______________________________________________ devel mailing list devel@ntpsec.org http://lists.ntpsec.org/mailman/listinfo/devel
