From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?UTF-8?Q?G=C3=A1bor_Boskovits?= Subject: Making javadoc reproducible Date: Fri, 12 Oct 2018 19:00:14 +0200 Message-ID: Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:59695) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gB0nj-00067W-AQ for guix-devel@gnu.org; Fri, 12 Oct 2018 13:00:36 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gB0nh-0006KZ-G1 for guix-devel@gnu.org; Fri, 12 Oct 2018 13:00:34 -0400 Received: from mail-io1-xd33.google.com ([2607:f8b0:4864:20::d33]:38270) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1gB0ng-0006Dm-5y for guix-devel@gnu.org; Fri, 12 Oct 2018 13:00:33 -0400 Received: by mail-io1-xd33.google.com with SMTP id n5-v6so9718181ioh.5 for ; Fri, 12 Oct 2018 10:00:26 -0700 (PDT) List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: Guix-devel Hello guix, I've tracked down the javadoc timestamp problem. There is a command line flag for javadoc (notimestamp), that disables generating the comment in the docs that contains the timestamp. Currently I see two ways forward: 1. Track down the calls to javadoc, and add the flag to all calls. 2. Write a simple patch to make javadoc behave as if notimestamp was specified, whenever SOURCE_DATE_EPOCH is defined. I do not think, that the patch produced by 2 is upstreamable, but it seems much less work. WDYT?