On Tue, Jul 15, 2008 at 2:57 PM, C. Scott Ananian <[EMAIL PROTECTED]> wrote:
> 2008/7/15 Jameson Chema Quinn <[EMAIL PROTECTED]>: > > If you have a better idea of how Glucose should handle these issues, > please > > share it. Simplifying assumptions are good, even if they're not 100% > valid. > > Versions in activity.info files are either plain integers, or > RPM-standard version strings, with no pretense that these correspond > in any way to sugar major releases or anything at all, except that > they are ordered: if the activity updater sees that you have version > N, and there is a version M announced[*] as compatible with your build > where M > N, then it will suggest that you upgrade to M. All other > meanings are encoded with other mechanisms. > --scott > How can you argue this and still argue that we can get away with integer version numbers? According to this logic, a when brand new activity(x) for OS(y) is released at time (t) and a bugfix activity(x+1) for OS(y-1) is released at time (t+1), anyone on OS(y) is going to try to update to the "newer", larger, activity(x+1) version, with none of the new features. - Eben
_______________________________________________ Devel mailing list [email protected] http://lists.laptop.org/listinfo/devel
