Bug#742864: Update to jdk8u20-b18

[Thomas Klute <thomas2.klute@uni-dortmund.de>]

Am 18.06.2014 14:55, schrieb Emmanuel Bourg:
> Even if removing the generated files could avoid mistakes like updating
> the control file but not its template, I lean toward keeping them for
> the convenience. Checking out the package and not seeing debian/control
> could also be confusing.

I disagree. Having a generated file in the source repository is
surprising and thereby confusing. I assumed I had to change the g++
dependency precisely for that reason. Sure, I would have been surprised
if the checkout had not contained a debian/control file, but then I
would have checked what's going on and subsequently understood.

Equally, convenience is actually a point against keeping a generated
control file in the repository: People will need to regenerate the file
for their build systems and then will have local changes that cannot be
merged upstream. This is generally annoying, and especially with Git
operations that require a clean tree.

Of course, the debian/control file would belong in a source package for
a specific version. In my opinion the clean solution is to ignore
generated files for the VCS tree, and if that requires many preparation
steps before build, script them.

Kind regards,
Thomas