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
