Re: Install munge-texi.pl for use by packages?

[Olaf Till]

On Mon, Jul 07, 2014 at 10:53:45PM +0200, Olaf Till wrote:
> On Mon, Jul 07, 2014 at 02:46:04PM -0400, John W. Eaton wrote:
> > <snip>
> > 
> > If we do go down this path, then I suppose a solution for cross
> > compiling would be to require that we build (or use, if it is
> > already installed on the system) a corresponding native version of
> > Octave that can be executed on the build system to generate the
> > figures and perform the munge-texi step.
> 
> I didn't see first that munge-texi.pl uses DOCSTRINGS files generated
> by mkdoc.pl. So either mkdoc.pl also would have to be converted to an
> Octave function, or the Octave function for munge-texi should use
> `get_help_text()' instead of DOCSTRINGS files. Intuitively I'd like
> the latter better, but are the DOCSTRINGS files also needed for other
> things? And using `get_help_text()' would require always to have the
> _same_ Octave version locally installed for cross-builds, since the
> help texts would be taken from the installed version ...

Weighing this up I'd now cowardly say the costs of this change are
higher than the advantage. Maybe a solution as pointed out by Mike:

On Mon, Jul 07, 2014 at 12:50:14PM -0400, Mike Miller wrote:
> Take a look at the communications package doc directory [1] for what I
> did to solve the exact problem you are looking at. Before tarring up
> the package to upload to sourceforge, I make the info documentation so
> it is part of the package distribution.

is more adequate.

Olaf

-- 
public key id EAFE0591, e.g. on x-hkp://pool.sks-keyservers.net

signature.asc
Description: Digital signature