On Tuesday, 18 October 2005, at 10:30:01 (+0800), Didier Casse wrote: > My Perl program reads from your CVS configure.in (or fo some packages > like embrace it's configure.ac) to pickup the current version. E.g. > (line 25) > > AM_INIT_AUTOMAKE(Eterm, 0.9.4) > > That's how it's able to keep track of some of those version changes of > the packages in CVS. > It worked well so far. It might not be the best solution but it's one > way of seeing it.
It's not the version number I'm worried about. It's the release number. Pre-release RPM's should have release numbers of 0.<something> rather than 1.<something>. The current spec files in CVS do this. > When Eterm is officially released, I'll just make a big announcement > to wipe out the *old* one. The close to 10,000 users that hang on to > the repo read my news page. :) It's your repo, so it's your call. I'm just pointing out the way to do it seamlessly. :) > Maybe this form would have been better > Eterm-0.9.3.999-1.20051016cvs.i386.rpm Heck no! That asparagus crap is raster's doing, not mine. The system I use has allowed for seamless RPM upgrades for the past 5 years, and I don't plan on obfuscating it with ridiculous version numbers now. :-P Michael -- Michael Jennings (a.k.a. KainX) http://www.kainx.org/ <[EMAIL PROTECTED]> n + 1, Inc., http://www.nplus1.net/ Author, Eterm (www.eterm.org) ----------------------------------------------------------------------- "Even if it takes forever to win your heart and your love and your devotion, I know it's going to be worth the wait." -- Amy Grant, "Say You'll Be Mine" ------------------------------------------------------- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
