-2 is correct for me, since I already submitted a patch for the installer script and updated the 6.3.0 installer some days ago. Now I need to figure out how to introduce some changes in the GRASS regkey layout to let the installer recognize if the current installed GRASS (if present) is the latest release or not, and thus decide if update the installed copy. A the moment, the GRASS release is deteminated by the SVN revision number; it represents binaries built upon different source code distributions. I think that I should introduce a new code number, that represents releases with differences in binaries, libraries, install script patches... that is all but not differences in GRASS source code: I could call it BNR (Binary Release Code) and start it with 0 every time the SVN rev number has changed in the binary release. What do you think about? Marco ________________________________
Da: Hamish [mailto:[EMAIL PROTECTED] Inviato: gio 15/05/2008 4.33 A: [EMAIL PROTECTED]; grass-dev@lists.osgeo.org; Michael Barton Oggetto: Re: R: [GRASS-dev] Re: [GRASS GIS] #160: WinGRASS: v.report>incompatability issue Marco: > > Yes. The new installer is already in my GRASS folder. > > Just tell me if upload it or not (and with what name, > > 6.3.0-1?) or -2. > I don't think you need to version your installer. GRASS > is the same version > that it was previously, you have just updated the GRASS > installer. So I'd > just put a date on it so that people know it's newer > than the old installer. > In fact, I would not change the version because that > implies a different version of GRASS. the typical (linux) convention is to label by source code version then "-" package revision. so 6.3.0-2 would seem appropriate here. For source code changes and extra "." is used, like "6.3.0.1". I would hesitate to put the date in there unless it is a SVN snapshot or the line of package revisions is someway broken. If date is used, please use a sortable way like YYYYMMDD. Hamish
_______________________________________________ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
