LaunchD versioning

[GoogleCodeExporter]

With Munki2, the launchD version keeps increasing, but there isn't any 
discernible changes. 

As the launchD requires a restart, my test clients are continually having to 
restart.

Original issue reported on code.google.com by eriknico...@gmail.com on 25 Jun 2014 at 1:08

[GoogleCodeExporter]

I've noticed this as well, but haven't had the time to figure out what's 
causing it. Feel free to dig in and investigate. 

Original comment by gregnea...@mac.com on 25 Jun 2014 at 1:58

[GoogleCodeExporter]

This seems to be triggered when I do a git pull from someone else's clone; it 
seems to cause the counting algorithm to be disturbed.

git isn't really a linear CVS and so counting commits to get a revision number 
has always been a bit of a hack. That hack has now broken. I'll need to do some 
thinking about how best to deal with the issue going forward.

It's really nice to not have to remember to manually bump versions when making 
a new release, so I don't want to return to that method. But it's also 
important to not require unnecessary installs/reinstalls of the launchd pkg.

Original comment by gregnea...@mac.com on 25 Jun 2014 at 6:07

[GoogleCodeExporter]

I have a fix for the issue, but it's going to trigger its own set of questions, 
as implementing it will result in the launchd pkg version _decreasing_  back to 
what it "should" be. For a "real" release this won't be an issue, and for 
people who haven't installed Munki 2 yet, they won't even notice it. Hmm. Need 
to think a bit before deciding how to proceed.

Original comment by gregnea...@mac.com on 25 Jun 2014 at 6:42

[GoogleCodeExporter]

I've posted on munki-dev for feedback and discussion.

Original comment by gregnea...@mac.com on 25 Jun 2014 at 9:36

[GoogleCodeExporter]

Fixed as of 2.0.0.2089. This also reverts the version of the launchd pkg to 
2.0.0.1969.

Original comment by gregnea...@mac.com on 27 Jun 2014 at 5:48

• Changed state: Fixed