From mboxrd@z Thu Jan 1 00:00:00 1970 From: Olaf Hering Subject: Re: [PATCH 3/5] INSTALL: mention variables for reproducible builds Date: Wed, 25 Mar 2015 09:49:58 +0100 Message-ID: <20150325084958.GB11487@aepfle.de> References: <1426872279-5001-1-git-send-email-olaf@aepfle.de> <1426872279-5001-4-git-send-email-olaf@aepfle.de> <1427212529.21742.451.camel@citrix.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: <1427212529.21742.451.camel@citrix.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Ian Campbell Cc: Keir Fraser , Tim Deegan , Ian Jackson , Jan Beulich , xen-devel@lists.xen.org List-Id: xen-devel@lists.xenproject.org On Tue, Mar 24, Ian Campbell wrote: > On Fri, 2015-03-20 at 18:24 +0100, Olaf Hering wrote: > > +Some components of xen and tools will include an unpredictable timestamp > > +into the binaries. To allow reproducible builds the following variables > > +can be used to provide fixed timestamps in the expected format. > > +XEN_BUILD_DATE=any > I'm not sure what this implies I'm allowed to pass here... Any string would do, if I read the code correctly. Would this be more obvious? XEN_BUILD_DATE= Olaf