Dne �t 16. dubna 2013 Darrell Anderson napsal(a): > >I have one small suggestion. Script r14-xdg-update writes to the > >configuration key Updated. If the script could contain internal > >version > >number (or timestamp), it could to key Updated write this value > >and then > >this value use to decide whether to execute again or not. > > > >Such solution could cover any subsequent updates. And it would not > >depend on testing the specific renamed files. What do you think? > > Sounds like a good idea. > > I never envisioned needing the script long-term, but I'm horrible > at predicting the future. Hopefully by the time R15 is the main > trunk in GIT we no longer need the script. Until then, perhaps we > should embrace your suggestion. :) > > Currently we use the following: > > [R14 XDG Updates] > Updated=true > > Perhaps change that to: > > [R14 XDG Updates] > R14.0.0-Updated=true > > If we do that then what mechanism do we use in the script itself to > track this? I'm thinking of corner cases such as a user updates > from 3.5.13.1 to R14.0.2 or something like that. Corner cases > always ruin parties. :) > > Darrell > I was thinking a little bit different way - for example: [R14 XDG Updates] Updated=R14.0.0 or (maybe better - can cover also changes during development versions and also easier for comparison in shell) [R14 XDG Updates] Updated=20130407 Where timestamp is not date of the conversion for user, but the internal date of r14-xdg-update script, which make conversion. Slavek --