From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Date: Sat, 29 Feb 2020 09:48:28 +0100 From: Michael Olbrich Message-ID: <20200229084828.GI3627@pengutronix.de> References: <20200227144449.29660-1-ada@thorsis.com> <20200227144449.29660-3-ada@thorsis.com> <20200228101609.hq5ubu5zqi6xfklx@pengutronix.de> <20200228154010.t3qdmkrtcojxyf6w@pengutronix.de> <20200228161441.ndqubgbnf4mi4vza@falbala.internal.home.lespocky.de> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <20200228161441.ndqubgbnf4mi4vza@falbala.internal.home.lespocky.de> Subject: Re: [ptxdist] [PATCH 2/3] os-release: Make date string reproducible List-Id: PTXdist Development Mailing List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: ptxdist@pengutronix.de Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: ptxdist-bounces@pengutronix.de Sender: "ptxdist" To: ptxdist@pengutronix.de, Alexander Dahl Hi, On Fri, Feb 28, 2020 at 05:14:41PM +0100, Alexander Dahl wrote: > On Fri, Feb 28, 2020 at 04:40:10PM +0100, Roland Hieber wrote: > > Instead we could use the date of ./tarball-version (like > > PTXDIST_BSP_AUTOVERSION does too) or the current VCS commit; or if the > > BSP is not a VCS repo, or if the worktree has local changes, fall back > > to searching for the most recent file in the current BSP. > > Or the user could just do anything she wants and feed it into > REPRODUCIBLE_TIMESTAMP_CUSTOM? How about - 'now' (what we have now) - 'last commit' (CommitDate fromt the last commit) - 'custom' (from a string) I'm not sure what you'd want to put in a custom string, but I wouldn't mind adding it. Michael -- Pengutronix e.K. | | Steuerwalder Str. 21 | http://www.pengutronix.de/ | 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 | Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 | _______________________________________________ ptxdist mailing list ptxdist@pengutronix.de