On 2/18/25 10:46 AM, Julien Plissonneau Duquène wrote:
I'm thus proposing the following policy from now on, to be revisited after the
toolchain is fixed and we see how it goes with a few JDK and build tool updates
(so maybe 3 years from now, let's say 2028):
- maintainers may at their discretion drop -java-doc packages rather than fix
them when they encounter build issues
- other maintainers may (re-)introduce them at their discretion
- new library packages may introduce new -java-doc packages and that "may" will revert to
a "should" (as in the currently published Debian policy for Java) once the toolchain is
sufficiently improved.
What do you think of that?
I doubt those "other maintainers" have the discipline to target their uploads
reintroducing -java-doc packages to experimental where they'll land after NEW processing.
I also wouldn't appreciate having to drop the reintroduced -java-doc package
again when its breaks with the next JDK update.
People who value java-doc package should maintain them separately to not bother
the maintainers who don't care for them. The separately maintained gcc -doc
packages might serve as an example.
Kind Regards,
Bas
--
GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
