From owner-freebsd-bugs Wed Jan 30 18:38:45 2002 Delivered-To: freebsd-bugs@freebsd.org Received: from mail20.jump.net (mail20.jump.net [206.196.91.20]) by hub.freebsd.org (Postfix) with ESMTP id 7BCB137B402; Wed, 30 Jan 2002 18:38:42 -0800 (PST) Received: from Powerbook.Dataplex.Net (cust-92-208.customer.jump.net [207.8.92.208]) by mail20.jump.net (8.11.6/) with ESMTP id g0V2caA16511; Wed, 30 Jan 2002 20:38:36 -0600 (CST) Date: Wed, 30 Jan 2002 20:38:39 -0600 Subject: Re: conf/6346: Kernel version strings need to relate to the source not the build Content-Type: text/plain; charset=US-ASCII; format=flowed Mime-Version: 1.0 (Apple Message framework v480) Cc: joe@tao.org.uk, sheldonh@FreeBSD.ORG, freebsd-bugs@FreeBSD.ORG, bde@zeta.org.au To: "."@babolo.ru From: Richard Wackerbarth In-Reply-To: <200201310026.DAA16945@aaz.links.ru> Message-Id: Content-Transfer-Encoding: 7bit X-Mailer: Apple Mail (2.480) Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org 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? > And #include 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. 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. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message