I don’t enjoy this topic at all, but I feel obligated to contribute some relevant links.
A previous discussion on the packaging mailing list[1] concluded that it doesn’t seem possible to package HTML documentation generated by almost any system, including at least Sphinx, Doxygen, and mkdocs, in a way that complies with guidelines around pre-compiled and bundled JS, CSS, and fonts. See also [2], which started that discussion.
There might be a conflict between this situation and certain language-specific guidelines that prescribe packaging standardized documentation packages. For example, [3].
[1] https://lists.fedoraproject.org/archives/list/packaging@lists.fedoraproject.... [2] https://bugzilla.redhat.com/show_bug.cgi?id=2006555 [3] https://bugzilla.redhat.com/show_bug.cgi?id=2097267
On Wed, Aug 10, 2022, at 3:35 PM, Jerry James wrote:
On Wed, Aug 10, 2022 at 1:24 PM Dan Čermák dan.cermak@cgc-instruments.de wrote:
Yes, but AFAIK HTML documentation also pulls in fonts.
True, although at least a couple of python-sphinx themes take pains to symlink to fonts rather than copy them (python-sphinx_rtd_theme and python-pydata-sphinx-theme come to mind). I presume that the symlinking approach means that we don't need to mention the font licenses in the License field, but it would be nice to have Richard confirm that.
But then you still have the various CSS, JavaScript, image and who knows what else files, of course. -- Jerry James http://www.jamezone.org/ _______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue