On Thu, 22 Oct 2009, Rainer Gerhards wrote: > David, > > I like this idea, but I have to admit I have not even the slightest clue on > how I should implement it...
I don't know either, but I do know a couple projects that do implement it. git implements it the linux kernel implements it if LOCAL_VERSION_AUTO is enabled in the config if I get a chance I'll try to dig into their makefiles to find out how. David Lang P.S. I don't know what rsyslog does with the version number, but when I use checkinstall to create a package from the source it ends up detecting the version number many times instead of once so instead of version='5.3.2' I get version='5.3.2 5.3.2 5.3.2 5.3.2 5.3.2 5.3.2 5.3.2 5.3.2 5.3.2 5.3.2 5.3.2' > Rainer > >> -----Original Message----- >> From: [email protected] >> [mailto:[email protected]] On Behalf Of [email protected] >> Sent: Thursday, October 22, 2009 9:30 PM >> To: rsyslog-users >> Subject: [rsyslog] version numbers from git repository >> >> I've been doing a lot of testing and can have a dozen >> different copies of >> rsyslog that all claim to be the same version number. >> >> the ability of git to give more precise versions (as described in the >> message from the git mailing list below) would be handy in >> eliminating >> confusion. >> >> the nice thing is that if a person is using a tagged version, >> this just >> reports the tag with nothing extra, so changing the makefile >> to use this >> would not affect most people. >> >> David Lang >> >> ---------- Forwarded message ---------- >> Date: Thu, 22 Oct 2009 10:01:25 +0200 >> From: Martin Langhoff <[email protected]> >> To: Robin Rosenberg <[email protected]> >> Cc: [email protected], [email protected] >> Subject: Re: Deciding between Git/Mercurial >> >> On Sun, Sep 27, 2009 at 8:01 PM, Robin Rosenberg >> <[email protected]> wrote: >>> s?ndag 27 september 2009 14:24:32 skrev Anteru >> <[email protected]>: >>>> Mercurial's revision number system: With git, I get an >> SHA1 hash for >>>> every commit, but it's not possible to see whether Hash1 >> is newer than >>>> Hash2, while Mecurial also adds a running number to each >> commit. What's >>> >>> But those numbers cannot be communicated since they are >> local to your >>> clone. >> >> You can use git-describe, which will look for the latest tag, and make >> a combo of latest tag, commits since the tag, short form of sha1. So >> you get "v1.6.3-33-g1234" - 33 commits after 1.6.3. Works very well to >> integrate in versioning. The git project itself uses it in the >> Makefile to set the versions, same as the kernel folk do -- I use it >> to version even RPM/DEBs. >> >> hth, >> >> >> >> m >> -- >> [email protected] >> [email protected] -- School Server Architect >> - ask interesting questions >> - don't get distracted with shiny stuff - working code first >> - http://wiki.laptop.org/go/User:Martinlanghoff >> -- >> To unsubscribe from this list: send the line "unsubscribe git" in >> the body of a message to [email protected] >> More majordomo info at http://vger.kernel.org/majordomo-info.html >> _______________________________________________ >> rsyslog mailing list >> http://lists.adiscon.net/mailman/listinfo/rsyslog >> http://www.rsyslog.com >> > _______________________________________________ > rsyslog mailing list > http://lists.adiscon.net/mailman/listinfo/rsyslog > http://www.rsyslog.com > _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com
