Hi,
Le 2025-02-18 10:59, Sebastiaan Couwenberg a écrit :
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'm not sure this is much of an issue. Maybe you could elaborate why you
think so?
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.
I'm not against the principle, but this isn't workable for javadocs.
gcc-N-doc has separate source files and its own build system (and even a
different, non-DFSG license). javadoc source is embedded in source code,
and its build more or less tightly integrated with the binaries build
system. Having different maintainers for those would mean duplicating
the entire source code as a new source package, which is obviously not
something that would be reasonable to do.
Cheers,
--
Julien Plissonneau Duquène
