Re: [OctDev] Octave Forge spec file

[Paul K. <pki...@us...>]

Quentin H. Spencer wrote:

> Hello,
>
> I mentioned on this list a while back that I have created a spec file 
> for building RPMs of octave-forge. Paul suggested putting it in admin, 
> which sounds good to me, but now I'm working on autoconfiguration. I 
> need to determine the octave version and the octave-forge version and 
> insert them into the spec file. As far as I can tell, this can happen 
> at one of three different stages: autogen.sh, configure, or the 
> release.sh script. My natural inclination is to do it in the configure 
> script, but the release.sh script appears to be the only place where 
> the octave-forge version is updated for version.h, and it seems like 
> it would make sense to do it in the same place. Comments?

When building from CVS, tag OCTAVE_FORGE_VERSION.m
with the date on which you downloaded the CVS snapshot.
It doesn't really matter when you tag the spec file, so long as
you get the version number from OCTAVE_FORGE_VERSION. 
Personally, I would create an entry in admin/spec/Makefile to do
the tagging so that all the rpm details stay together.

To keep version numbering consistent, please break the
relevant lines from release.sh into admin/tag_version.sh
or some such so that you don't need to run release.sh to
build an RPM from a cvs snapshot.

Paul Kienzle
pki...@us...