Date: Mon, 15 Mar 2010 18:41:01 -0700 From: Doug Barton <dougb@FreeBSD.org> To: "M. Warner Losh" <imp@bsdimp.com> Cc: freebsd-current@freebsd.org Subject: Re: [PATCH] newvers.sh Message-ID: <4B9EE1AD.9080805@FreeBSD.org> In-Reply-To: <20100315.193455.69510145151660650.imp@bsdimp.com> References: <20100313.211303.585238797224891349.imp@bsdimp.com> <20100316004117.GB36963@dragon.NUXI.org> <4B9EDB05.4020800@FreeBSD.org> <20100315.193455.69510145151660650.imp@bsdimp.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 03/15/10 18:34, M. Warner Losh wrote: > In message: <4B9EDB05.4020800@FreeBSD.org> > Doug Barton <dougb@freebsd.org> writes: > : On 03/15/10 17:41, David O'Brien wrote: > : > I'd rather not introduce yet more special things that have to be done > : > before invoking newvers.sh. > : > : David, > : > : Trying to understand what you're getting at here. What's your use case > : for invoking newvers.sh from the command line? AFAIK it's only every > : used as part of the build process. Once by the kernel build and once for > : library related stuff (IIRC). > > It is used in the kernel build (in a couple of different places) and > in include/Makefile to generate osreldate.h. Well, includes are related to libraries, right/ :) > I believe the latter can be simplified to not require it. When I last looked at it I vaguely recall thinking that not needing newvers.sh for that purpose was a good goal, but ENOTIME. Thanks for refreshing my memory, Doug -- ... and that's just a little bit of history repeating. -- Propellerheads Improve the effectiveness of your Internet presence with a domain name makeover! http://SupersetSolutions.com/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4B9EE1AD.9080805>