Let's just do what Wim Villerius suggested: if we find a .CVS, use it as version number, else use version number read from a simple VERSION file. This all can be calculated at very begining of configure script, before defining version number :) Mark Wedel wrote: > Alex Schultz wrote: > >> Tchize wrote: >> >>> Maybe a ./configure --release=<version number here> >>> :) >>> >> I really like that idea, except for one issue. People compiling from >> source releases typically wouldn't do that, so I think that what would >> be better than including that in the ./configure, would be having a >> simple script that could be run as part of the release process. >> > > Updating the version number requires the update of the configure.ac script > (then it builds the correct package, etc). Likewise for the rpmspec file. > > However, doing something like ./configure --debuglevel=0 does work, because > the rpmspec, which at least is used for rpm building, does have the configure > line it uses, so modifying that to include the debug option works just fine > and > dandy. > > I'll look at doing that. > > _______________________________________________ > crossfire mailing list > [email protected] > http://mailman.metalforge.org/mailman/listinfo/crossfire > >
_______________________________________________ crossfire mailing list [email protected] http://mailman.metalforge.org/mailman/listinfo/crossfire
