EDITION number

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

EDITION number

Rik-4
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).


--Rik

Reply | Threaded
Open this post in threaded view
|

Re: EDITION number

John W. Eaton
Administrator
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

Reply | Threaded
Open this post in threaded view
|

Re: EDITION number

Rik-4
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.

 @titlepage
 @title GNU Octave
 @subtitle A high-level interactive language for numerical computations
-@subtitle Edition @value{EDITION} for Octave version @value{VERSION}
+@c FIXME: Would like to use @value{EDITION} but this variable is the
+@c        same as VERSION and contains MAJOR.MINOR.PATCH.  The variable
+@c        is automatically generated by Automake in version-octave.texi.
+@c        Need to use sed to strip off MINOR.PATCH numbers and place
+@c        the results in a new file, and then @include that new file.
+@subtitle Edition 4 for Octave version @value{VERSION}
 @subtitle @value{UPDATED-MONTH}
 @sp 2
 @multitable @columnfractions 0.4 0.025 0.65

--Rik