[meego-packaging] package version and his control

[fathi.boudra at nokia.com]

> Just because you would have used it doesn't mean it isn't crazy,
> and it also doesn't mean you are following Debian's packaging policy.
> As you can see from their policy: http://www.debian.org/doc/debian-policy/ch-controlfields.html#s-f-Version you are not compliant.

[OT] I am compliant otherwise my packages wont't be accepted ;)

> If you are packaging a 'beta' product, you can explain that inside either packaging format (rpm or deb).

That's the point of my mail, what are the best practice for handling snapshot.

> This is not something you encode in the version string.

And why not ?

> Secondly, how does a unique git number help anyone aside from the packager?
> Remember you are creating packages for public consumption by scripts and humans, not for yourself.

Nobody care about the version, especially not the humans.
Only the packager cares because he needs to handle package upgrades, etc...
The versioning isn't for them. The end user do "install my app", not "install my app version whatever".