On 18/09/09 00:38, Pieter de Bie wrote: > #define LONG_VERSION 0.7.13 > #define GIT_VERSION v0.7-13-g7bfcf9a > #define SHORT_VERSION 0.7 > > so, if I want Sparkle to update, I need to call it at least 0.7.14... > > I don't think the long version is that important, we only used it to > display something in the about dialog, I think. Is it OK to just set > it to SHORT_VERSION instead? Or is there some interaction I'm > forgetting?
Right, now that my correct patch for git-describe is in I don't see any point in setting this other than 0.7.1. We only need one machine-generated output and the .13 was just a stupid workaround anyway. So I think we can go back to manually setting this (or getting it from the tags, though the first way is easier). Sorry I'm not that active atm, learning for an exam about pretty abstract stuff and trying not to be distracted too much ;) Greetings, Jojo -- Johannes Gilger <[email protected]> http://heipei.net GPG-Key: 0x42F6DE81 GPG-Fingerprint: BB49 F967 775E BB52 3A81 882C 58EE B178 42F6 DE81
