Jesse Becker wrote: > On Fri, Sep 18, 2009 at 08:58, <daniel.poc...@barclayscapital.com> wrote: > >>> Fair enough. I didn't realize it was a recent addition, and >>> given the long %changelog, was surprised to see it still at >>> "1". I'll add a note in the specfile about updating it, and >>> bump the version in trunk. >>> >> I've noticed different ways of doing this, too >> >> Sometimes I see: >> >> 1.0-1 >> 1.0-2 >> 1.1-1 (release number reverts back to 1 on new version of code) >> 1.1-2 >> >> and other projects do something like: >> >> 1.0-1 >> 1.0-2 >> 1.1-2 (nothing changed in spec file, release number unchanged) >> 1.1-3 >> >> Is there any preference for how this should work in Ganglia? Can it be done >> in a unified way across packaging systems, or should we avoid any such >> unification? >> > > I prefer a monotonically non-decreasing release number (the 2nd option). > > I think it has always been 1 because the former approach was used, or maybe because it just isn't documented in the release procedure
I actually don't think the release number is that important overall, for a few reasons: - in both of the schemes suggested above, RPM would sort the versions in the same order anyway - I can't see that there have been any releases of Ganglia where the release number has been included in the name of the tag - I can't see that there are any releases where the spec file was the only change However, if/when necessary, we could start creating multiple tags of the same version, including the release number in the tag name, where only the spec file changes, or where the only change is an improvement for the init script or config file. As noted before, @REL@ is used in solaris/pkginfo (see trunk), and it is also intended for WiX/ganglia-gmond.wxs (also in trunk), so whatever the final decision, it may be desirable to support all of those. We could also have separate variables, @REL_RPM@, @REL_PKG@, @REL_WXS@, etc For 3.1.3, I'm leaving it as it is now, the release number is in configure.in ------------------------------------------------------------------------------ Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf _______________________________________________ Ganglia-developers mailing list Ganglia-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ganglia-developers
