[Pkg-octave-devel] Processing of octave2.9_2.9.7-2_i386.changes

[Rafael Laboissiere]

* John W. Eaton <jwe at bevo.che.wisc.edu> [2006-08-18 14:48]:

> Did you see the message I sent earlier?

No.

> I don't know if it made it to the list yet.  I received the following
> bounce notice about it:
> 
>      ----- Transcript of session follows -----
>   ... while talking to lists.alioth.debian.org.:
>   >>> DATA
>   <<< 451 Could not complete sender verify callout
>   <pkg-octave-devel at lists.alioth.debian.org>... Deferred: 451 Could not complete sender verify callout
>   [snip]

Yes, some Debian hosts are having problems now.

>   Building the docs should not be required unless one of the following
>   changes when doc/conf.texi is generated when Octave is built:
> 
>   [snip]

Thanks for the explanations.  In the case of the Debian package, the
documentation is rebuilt because I need to generate info files with
different names (octave2.1.info and octave2.9.info).  The @setfilename
*.texi files are then changed accordingly.  Without this changes, the
octave2.1-info and octave2.9-info would conflict with each other.

> If we set OCTAVEHOME to be /usr/local on all systems instead of
> setting it at build time, the manual for Octave on Debian systems will
> tell people to look in /usr/local/share ... which doesn't exist.
> Should we care?  If not, then I can make this change and the docs
> should not be rebuilt when building the Debian package.

The conf.texi files are not changed in the Debian package. As a result,
we ship the documentation with some incoherences, as you mentioned in
your post.  Since we have to rebuild the docs anyway (see above), I will
add a patch for changing OCTAVEHOME.

That said, I am working now on a way to avoid the documentation being
built by the autobuilders.

-- 
Rafael