[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Manual for GNU Octave package (Octave-Forge)
|
From: |
Mike Miller |
|
Subject: |
Re: Manual for GNU Octave package (Octave-Forge) |
|
Date: |
Mon, 27 Apr 2015 14:43:42 -0400 |
On Mon, Apr 27, 2015 at 18:48:34 +0100, Carnë Draug wrote:
> On 26 April 2015 at 11:32, Oliver Heimlich <address@hidden> wrote:
>>
>> 2. Should I bundle any compiled version of the manual in the package release
>> tarball? Or should I leave this to downstream distributors? Are there any
>> conventions, which downstream distributors expect?
>>
>
> I believe it's preferable to have compiled pdf and texi on the release.
> Downstream can always rebuild them, no problem. Octave releases have
> builds of the manual too.
With the latest communications package release, I went with building
the Info format in the tarball release, and let the user or packager
build other formats if they want. I think this is typical for GNU
projects. But yes, Octave does build and include Info, PDF, PS, and
HTML formats in the release tarball.
--
mike