Re: misc/47095: MKREPRO=yes is unacceptable for releases

[Alan Barrett <apb%cequrux.com@localhost>]

The following reply was made to PR misc/47095; it has been noted by GNATS.

From: Alan Barrett <apb%cequrux.com@localhost>
To: gnats-bugs%NetBSD.org@localhost
Cc: 
Subject: Re: misc/47095: MKREPRO=yes is unacceptable for releases
Date: Sat, 20 Oct 2012 12:32:09 +0200

 On Sat, 20 Oct 2012, jakllsch%kollasch.net@localhost wrote:
 >>Description:
 >MKREPRO=yes builds are unacceptable for release builds.
 >>How-To-Repeat:
 >install 6.0, be unable to find any useful information about who or what built 
 >the release
 >>Fix:
 >don't bulid releases with MKREPRO=yes
 
 I agree that this is problem, but I have a different idea for a 
 fix:
 
 Modify MKREPRO to allow it to insert sanitised information into 
 places like /etc/release, the output from sysctl kern.version, 
 and the output from uname -v.  Two MKREPRO builds with the same 
 sanitised information should be identical, but two MKREPRO builds 
 with different sanitised information should be different.
 
 I have been meaning to work on this, but I have not got around to 
 it.  For my own use, I want the framework to allow me to embed my 
 private branch name and revision number into the kernel version,
 along with comments like "testing a patch for PR nnnn", so that
 "uname -a" can help me verify that I booted the correct test kernel.
 
 --apb (Alan Barrett)