https://bugs.kde.org/show_bug.cgi?id=406177
--- Comment #3 from Harald Sitter <sit...@kde.org> ---
The biggest problem for me are paths that are compiled-in, the paths in the
dtd/xsl files I can probably sed out for something more suitable at
snap-buidtime. The binaries however are (currently) shared with regular deb
builds, so it's far less trivial to get those bent into shape if they don't
follow some environment variable.
I think relative paths would be fine for xsl/dtd and should work in all cases?
What I was thinking about with runtime generation is to actually mimic what
configure_file does currently, but at runtime.
e.g.
- install kde-include-man.xsl.tmpl
- at runtime meinproc figures out where the docbook-xml/docbook-xsl stuff
lives, or fall back to compiled in paths
- open kde-include-man.xsl.tmpl
- QString.replace("@XSL_PATH@", determinedPath);
- write to $tmpdir/kde-include-man.xsl
- load the generated file with the now runtime-dependent includes
Granted I don't know much about how docbook works, so that may be a nonsensical
idea.
If using relative paths would work, I think that'd be a sound solution that
should work both for relocated trees as well as regular ones.
--
You are receiving this mail because:
You are watching all bug changes.
