Cristian Le via python-devel <[email protected]> writes:
> On the technicality, yes overriding the references to local ones is > possible. > > But whose job will it be to maintain the reference correctness, e.g. the > sphinx build should fail on the could not resolve reference warning and > then does this get forwarded to upstream? > Maybe a similar process could be followed as branching for EPEL. The intersphinx mapping could be a subpackage of the main package. Someone could request if, if the maintainers of the package do not want to provide the intersphinx mapping, the person requesting could be added as a co-maintainer. > It would also mean that all other packages should strive to provide the > sphinx builds, and we standardize the install locations. I don't have > strong objections to it, it could help push more man and other format > generations, but iirc this is not quite a smooth journey on all projects. > The main thing is to standardize the install locations. Sphinx builds could be added gradually. > On 10/26/26 11:18, Benson Muite via python-devel wrote: >> Hi, >> >> When creating documentation for some python packages, there is often an >> intersphinx mapping needed. This needs to be loaded to the Fedora >> repositories, but will likely be duplicated for many packages. Would it >> be worth creating a standard way to upload and reference intersphinx >> mappings? >> >> This has come up in the following review: >> https://bugzilla.redhat.com/show_bug.cgi?id=2556387 >> >> Regards, >> Benson -- _______________________________________________ python-devel mailing list -- [email protected] To unsubscribe send an email to [email protected] 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/[email protected] Do not reply to spam, report it: https://forge.fedoraproject.org/infra/tickets/issues/new
