Bug#814954: libgcrypt20: add libgcrypt-mingw-w64-dev for cross-building to Windows targets

[Daniel Kahn Gillmor]

On Sun 2016-02-21 00:44:11 -0800, Andreas Metzler wrote:
> Why don't we simply hardcode this as 1, 2 or 42 instead? Having changing
> builds without source changes (just becuse the lenght of
> debian/changelog increased) seems wrong to me.

You're welcome to do this however you you think best, of course!  My
instinct was to try to somewhat match the flavor of upstream's
conception of the revision number: they have an indefinitely-changing
revision number.  I figured that the length of the debian/changelog
would actually be even better, since it is indefinitely-changing, but
always in a positive direction.  That way, if you re-build with a new
changelog, the resultant file will have a different revision number.

otoh, a simple hard-coded value is probably fine too :)

      --dkg