Date: Thu, 8 Aug 2019 16:51:42 -0700 (PDT) From: "Rodney W. Grimes" <freebsd-rwg@gndrsh.dnsmgr.net> To: Ed Maste <emaste@freebsd.org> Cc: tech-lists <tech-lists@zyxst.net>, "freebsd-arch@freebsd.org" <freebsd-arch@freebsd.org> Subject: Re: svn commit: r350550 - head/share/mk Message-ID: <201908082351.x78NpgBR094817@gndrsh.dnsmgr.net> In-Reply-To: <CAPyFy2BE6EymEbQ8qL=ATQjngMxy8byofUAWZPMTSQYrortd2w@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> On Wed, 7 Aug 2019 at 21:50, tech-lists <tech-lists@zyxst.net> wrote: > > > > really? When the setting first became available, I found it wasn't the case, > > and that's why on all my stable systems I had to set > > WITHOUT_REPRODUCIBLE_BUILD=YES in /etc/src.conf in order to preserve previous > > uname -a behaviour. > > WITH_REPRODUCIBLE_BUILD has never affected the method used to > determine the SVN version or whether it was included - the same SVN > version has always been in uname -a regardless of the > REPRODUCIBLE_BUILD knob. > > The REPRODUCIBLE_BUILD knob affects exactly two invocations in the > build process. When set -r or -R is passed tosys/conf/newvers.sh and > stand/common/newvers.sh. This controls timestamp, user, and host in > the loader, and the build count, time, date, user, host, and build > directory in the kernel (as reported by uname). Thank you for the clarification on this, if that infact is the only effect this knob has on all of the build artifacts I am completly fine with it set either way and shall continue to force it off on all my kernel build VM's so that I do have my critical host and path information when I need it. I formally retract my proposal. -- Rod Grimes rgrimes@freebsd.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201908082351.x78NpgBR094817>