Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 31 Jan 2002 07:01:18 +0300 (MSK)
From:      "."@babolo.ru
To:        rkw@dataplex.net (Richard Wackerbarth)
Cc:        joe@tao.org.uk, sheldonh@FreeBSD.ORG, freebsd-bugs@FreeBSD.ORG, bde@zeta.org.au, "."@babolo.ru
Subject:   Re: conf/6346: Kernel version strings need to relate to the source not the build
Message-ID:  <200201310401.HAA01299@aaz.links.ru>
In-Reply-To: <A1EEA90C-15F3-11D6-9809-0003930737AC@dataplex.net> from "Richard Wackerbarth" at "Jan 30, 2 08:38:39 pm"

next in thread | previous in thread | raw e-mail | index | archive | help
Richard Wackerbarth writes:
> On Wednesday, January 30, 2002, at 06:26 PM, "."@babolo.ru wrote:
> 
> > Richard Wackerbarth writes:
> >>
> >> I think we could actually do it just once (at the time that we update
> >> from the cvs?) and cache that result.
> >> That would get rid of at least a part of the delay.
> >>
> >> It can also be done by playing games on a special file in the master 
> >> cvs
> >> archive (but not the copies thereof)
> > Exactly.
> > What about do
> > date +'#define LAST_MOD "%Y-%m-%d %H:%M:%S"' > /path/last_mod_date.h
> > on any CVS tree update?
Sorry, commit

> > And #include <last_mod_date.h>
> 
> That won't work. It produces the time of the cvs checkout/update and not 
> the time of the source modification.
> That is little better than the time of the compile that we have now.
I think about commit time (my mistake, not checkout)
But I understand, it is slightly complex to generate
last_mod_date.h,v then last_mod_date.h,
but there no need in tags in it, so it can be whole
overwritten by every commit

> You need to modify the file as a part of the cvs commit process. The RCS 
> keyword $Date$ or equivalently one of the $Id$ variants such as 
> $FreeBSD$ gets the time associated with file modification rather than 
> file retrieval. Joe's method is functionally correct. We are now looking 
> for a more efficient method to accomplish the same thing.

-- 
@BABOLO      http://links.ru/

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200201310401.HAA01299>