[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: EDITION number
From: |
Rik |
Subject: |
Re: EDITION number |
Date: |
Wed, 11 Apr 2018 12:01:09 -0700 |
On 04/11/2018 11:30 AM, John W. Eaton wrote:
> On 04/11/2018 02:18 PM, Rik wrote:
>> jwe,
>>
>> The EDITION number used in the documentation is the same as the VERSION
>> number according to the documentation for Automake:
>>
>> |EDITION|
>> |VERSION|
>> Both of these macros hold the version number of your program. They
>> are kept separate for clarity.
>> Since we want EDITION to be just the base number (4, not 4.3.90) should
>> be post-process the generated version-octave.texi file with sed, or
>> should we just hardcode the EDITION number in the title page of
>> octave.texi and bump it when we make major releases (which isn't that
>> often).
>
> It seems more reliable to generate it automatically if possible. But I
> don't think it's something that needs to be done before the current release.
>
> jwe
>
>
I hardcoded the EDITION number for now.
address@hidden
address@hidden GNU Octave
address@hidden A high-level interactive language for numerical computations
address@hidden Edition @value{EDITION} for Octave version @value{VERSION}
address@hidden FIXME: Would like to use @value{EDITION} but this variable is the
address@hidden same as VERSION and contains MAJOR.MINOR.PATCH. The variable
address@hidden is automatically generated by Automake in version-octave.texi.
address@hidden Need to use sed to strip off MINOR.PATCH numbers and place
address@hidden the results in a new file, and then @include that new file.
address@hidden Edition 4 for Octave version @value{VERSION}
address@hidden @value{UPDATED-MONTH}
address@hidden 2
address@hidden @columnfractions 0.4 0.025 0.65
--Rik