From: Peter S. <pet...@ut...> - 2004-03-31 22:59:53
|
Well, I could parse through the _filename_ we are running as (evms-2.3.1.tar.gz) I think and get the version number that way, but that seems very non-ideal to me. At the time the spec file is used in "rpmbuild --tb evms-2.3.1.tar.gz there is nothing but the spec file in existance. So it is either manual spec file editting, or manual spec file generation. Other projects (like gaim for instance) are using a .spec.in file, but then again it looks like they are doing the "autoconf" _and_ a "./configure" before they wrap the whole thing up into the .tar.gz . That is messy. Tell me, which is best for evms? I'd like to work on getting more package-definition files going (such as deb, etc--maybe even some different architectures...) but updating the versioning is a necessity.. I personally think it would work best if we had a .sh script that updates the version # in specific files, just something simple, and you just run it to update the version before generating the .tar.gz .. Thing is I don't know what your process is to generate the .tar.gz . Peter Kevin Corry wrote: >On Wednesday 31 March 2004 12:36 pm, Peter Smith wrote: > > >>Kevin: I've run into a snag. I don't think autoconf is the correct >>place to have a version number plugged into evms.spec . Since you >>generate the .tar.gz manually and also generate the configure script >>using autoconf (I assume,) is there somewhere else I can get the version >>number for the spec file handled? You can see the difficulty here--if >>the evms.spec file gets generated by running configure, then creating an >>RPM directly from .tar.gz source will not work as it looks for the >>existance of the .spec file which isn't there yet. >> >> > >Yes, I can see how that is going to be a problem. > >I'm not sure how or if the version number can be auto-generated in evms.spec >if it needs to be present before running ./configure. There are only two >places that provide the EVMS version number. One is in configure.ac, which >generates the PACKAGE_VERSION number that evms.spec.in now uses. The other is >in make.rules.in, in the defines for MAJOR_VERSION, MINOR_VERSION, and >PATCH_LEVEL. But I'm not sure how those will be of any help either (you'd >have to run some shell code within the spec file to grep for and assemble the >version number). > >Perhaps this means we have to go back to the previous version of evms.spec.... > > |