Am 22.04.20 um 12:05 schrieb Mauro Carvalho Chehab: [...] >> The opposite of pointing to a file is, that we can only point the >> file not a content in the file and we lost the flexibility of >> dynamical referencing by target's name: If the target is moved, >> the refs has to be changed also. > > True, but we have a script that tracks those problems and even > auto-correct most of such broken references. [...] > An extension like Documentation/sphinx/automarkup.py could > easily replace them by :doc:`Documentation/foo`, creating > links on all those places at no cost. [...] > Adding explicit :ref: would require manual work, and I bet some > maintainers will reject adding extra markups on some files. [...] > In any case, maybe one day intersphinx will have support for :doc: > types added there as well. > > Without looking into the dirty details, it doesn't sound too hard to add > support for it: intersphinx could simply create a :ref: type of reference > for all files (like, __doc_driver_api__media__drivers__tuners). Then, > any place with a :doc:`/driver-api/media/drivers/tuner` would be > dynamically replaced by a :ref:`__doc_driver_api__media__drivers__tuners` > at runtime. Yes, hack over hack .. sometimes I feel back in the "DocBook century". We now have a very confusing build process and I have to admit that I am also to blame. I also believe that everyone has good reasons. For one solution or for the other solution. _Hack_ or _standard_, it is always a compromise that the Kernel community has to find. I cannot rate that. -- Markus --
