Re: Deployment of images with an info doc

[jemarch]

   > Ok, I will use that workaround, maintaining several sub directories in
   > doc/ for the different manuals.

   This sounds suboptimal. Can't you use a common figures directory
   with a name that includes the name of your package, e.g. gnupdf/ or
   gnupdf-figures/?

That would make it difficult to decouple the manuals after they get
installed.  Having gnupdf-arch.texi looking into gnupdf-arch-figures/
and gnupdf-hg.texi looking into gnupdf-hg-figures/ makes it possible
to relocate/copy/delete a deployed manual in a easy way.

   > Maybe we should suggest the maintainers to follow the same convention
   > too?  As time passes more and more projects would want to deploy the
   > images for graphics-enabled info readers...

   For LilyPond info documentation, "make install-doc" creates
   ${info_dir}/lilypond/, which is a symlink to the subdirectory of
   isntalled HTML docs tree which contains the images.

Ah, thanks for the info.

Incidentally the lilypond-doc Debian package is creating an empty
${info_dir}/lilypond directory.  I will report this.

-- 
Jose E. Marchesi  <address@hidden>
                  http://www.jemarch.net
GNU Project       http://www.gnu.org