Xiyue Deng <manp...@gmail.com> writes:

> Hi,
>
> Recently I am attempting to enable shipping docs of the racket-mode
> package[1].  However, its info page contains links to image files
> (e.g. [2]) using the image syntax[3].  If I simply handle the image
> files like the *.info files using debian/<package>.info, install-info
> will treat those files as info files and emit warnings, and lintian is
> not happy either.  I don't see suggestions in the Policy manual
> regarding how images should be handled[4].  I am currently thinking of 2
> ways to handle this situation:
>
> * Put the image files in another directory (either
>   /usr/share/doc/<package>/, or /usr/share/info/<package>-figures/ as
>   suggested by [3]), and patch the path in the texi source.
>

On further testing, this option doesn't really work: the texi file is
generated from an org file, and it doesn't seem to recognize image file
with path, so it skips the svg image and uses the alternative text
instead, which is not ideal.  So it looks like we have to use the
second alternative below.

I wonder whether it would be desirable to make dh_installinfo not
treating every file as info and handle images better.

> * Just put them together under /usr/share/info/, ignore the install-info
>   warnings, and add lintian-overrides.
>
> As linking images may become more popular over time, I wonder whether
> debhelper want to handle such case in a more uniform way, and I'd like
> to experiment with the suggestions.  It would be even better if there is
> a solution acceptable upstream so that I don't need to carry a patch.
>
> Thanks in advance!
>
> [1] https://salsa.debian.org/emacsen-team/racket-mode
> [2] 
> https://salsa.debian.org/emacsen-team/racket-mode/-/blob/master/doc/racket-mode.texi?ref_type=heads#L888
> [3] 
> https://www.gnu.org/software/texinfo/manual/texinfo/html_node/Image-Syntax.html
> [4] https://www.debian.org/doc/debian-policy/ch-docs.html#info-documents
>
> -- 
> Regards,
> Xiyue Deng

-- 
Regards,
Xiyue Deng

Attachment: signature.asc
Description: PGP signature

Reply via email to