From: "Gábor Boskovits" <boskovits@gmail.com>
To: Mykola Nikishov <mn@mn.com.ua>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: Making javadoc reproducible
Date: Sun, 19 May 2019 15:46:31 +0200 [thread overview]
Message-ID: <CAE4v=phxnnbx02va16Spu4Wxy4_P6FSiLdTvAixv0RwqPboNPg@mail.gmail.com> (raw)
In-Reply-To: <878sv2n4ve.fsf@think>
[-- Attachment #1: Type: text/plain, Size: 1063 bytes --]
Hello,
Mykola Nikishov <mn@mn.com.ua> ezt írta (időpont: 2019. máj. 19., V, 12:23):
> Gábor Boskovits <boskovits@gmail.com> writes:
>
> >> > Also we can simply turn off the timestamp generation
> >> > unconditionally...
> >>
> >> Number 2 sounds good, and why not giving it a try to place it upstream?
> >
> > Ok, i will go for it, and try to get it upsreamed for jdk8 and jdk11.
>
> Gábor, do you have anything to share?
>
>
It's not upstreamed, but our jdk11 javadoc is reproducilble.
Current status is that all outputs except the jdk could be easily made
reproducible.
Jdk is hard to solve, but the jre and javadoc are ok on jdk11. I plan to
package jdk12 soon,
then do a cleanup on the bootstrap toolchain.
For hints on the problem around jdk see:
https://hg.openjdk.java.net/jdk/jdk12/file/06222165c35f/make/scripts/compare.sh
from line 160.
That is the last reproducibility issue we have in jdk :)
--
> Mykola
>
> Libre/Free Java Software Developer
> https://manandbytes.gitlab.io/
>
>
> Best regards,
g_bor
[-- Attachment #2: Type: text/html, Size: 1950 bytes --]
next prev parent reply other threads:[~2019-05-19 13:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-12 17:00 Making javadoc reproducible Gábor Boskovits
2018-10-12 17:35 ` Gábor Boskovits
2018-10-12 18:01 ` Björn Höfling
2018-10-12 18:14 ` Gábor Boskovits
2019-05-19 9:57 ` Mykola Nikishov
2019-05-19 13:46 ` Gábor Boskovits [this message]
2018-10-12 18:42 ` Vagrant Cascadian
2018-10-13 21:06 ` Alex Vong
2018-10-14 3:35 ` Chris Marusich
2018-10-14 6:43 ` Gábor Boskovits
2018-10-14 19:19 ` Gábor Boskovits
2018-10-15 10:09 ` Danny Milosavljevic
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAE4v=phxnnbx02va16Spu4Wxy4_P6FSiLdTvAixv0RwqPboNPg@mail.gmail.com' \
--to=boskovits@gmail.com \
--cc=guix-devel@gnu.org \
--cc=mn@mn.com.ua \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).