Ignore:
Timestamp:
Dec 10, 2008, 4:49:53 AM (12 years ago)
Author:
jmpp@…
Message:

Finally move trunk away from floating point version numbers and instead use the more common x.y.z format, by:

  • Moving base/macports1.0/macports_autoconf.tcl.in to the @MACPORTS_VERSION@ autoconf variable;
  • Introducing a temporary special-case hack to force the selfupdate run in case the $macports::autoconf::macports_version variable is in the old format and smaller or equal to 1.800 (cf. my comment in the selfupdate proc in base/macports1.0/macports.tcl);
  • Removing the now unnecessary base/config/mp_version file, as everything is now determined from the base/config/macports_version file;
  • Removing the @MP_VERSION@ autoconf macro;
  • Regenerating the configure script;

All in all, we should have standard x.y.z version numbers starting from current trunk + 1 (e.g. 1.8.1), since
current trunk will only serve to introduce this code into users' hands first.

PS: I chose to force the upgrade as the special-case hack, since otherwise I'd have to reset the $macports::autoconf::macports_version
variable to achieve the same result, and that seems like it might make some babies out there cry...

File:
1 edited

Legend:

Unmodified
Added
Removed
  • trunk/base/portmgr/ReleaseProcess

    r32893 r43375  
    6767
    6868 * Update the file base/ChangeLog in both trunk and the release branch to reflect the appropriate changes.
    69  * Update the file base/config/mp_version with the target release number. Note that this is a floating
    70    point number that corresponds to the release number; it should correspond roughly to the release number
    71    where possible. Release 1.6.1, for instance, would be represented by the floating point number 1.610.
    72    The version number in mp_version is displayed by the port command as the version of MacPorts,
    73    and is used by the selfupdate command to determine whether a newer version of code is available.
    74    This number should be different between trunk and a release branch, the former greater to differentiate
    75    it from the latter.
     69 * Update the file base/config/macports_version with the target release number.  The version number in
     70   macports_version is displayed by the port command as the version of MacPorts, and is used by the selfupdate
     71   command to determine whether a newer version of code is available. This number should be different
     72   between trunk and a release branch, the former greater to differentiate it from the latter.
    7673 * Update the autoconf 'configure' script through the provided base/regen.sh script once the version number
    7774   in mp_version has been changed, since the former reads the latter.
Note: See TracChangeset for help on using the changeset viewer.