E.g. qpa/doc/chap6.html contains <a href="/Users/oyvinso/gap-4.11.0/doc/ref/chap62.html#X818DE6C57D1A4B33">
Note that ReleaseTools works hard to avoid this kind of problem -- one trick is that it uses PushOptions(rec(relativePath:="../../..")); before doing Read("makedoc.g") when building the documentation for a release. But that in turn is an AutoDoc feature, which you don't seem to be using to generate the documentation (it is useful for that even if the manual is pure GAPDoc). Anyway, I think all this ends up doing is pass "../../.." as final argument to MakeGAPDocDoc ?
(ReleaseTools also scans for such issues and will refuse to make a release if the manual contains such absolute links.)
E.g.
qpa/doc/chap6.htmlcontains<a href="/Users/oyvinso/gap-4.11.0/doc/ref/chap62.html#X818DE6C57D1A4B33">Note that ReleaseTools works hard to avoid this kind of problem -- one trick is that it uses
PushOptions(rec(relativePath:="../../.."));before doingRead("makedoc.g")when building the documentation for a release. But that in turn is an AutoDoc feature, which you don't seem to be using to generate the documentation (it is useful for that even if the manual is pure GAPDoc). Anyway, I think all this ends up doing is pass "../../.." as final argument toMakeGAPDocDoc?(ReleaseTools also scans for such issues and will refuse to make a release if the manual contains such absolute links.)