Hi, >> Looks good -- though we'll have to ponder how we want to handle epochs >> (now that the unversioned package needs to add one). Sean said that >> there was a DEP suggesting they be included in versions via "%", >> e.g. 1%20180414-1+git836dce6. >> >> I'm not sure what I think about that yet -- locally I've just created >> two tags VERSION and 1%VERSION. If there's no harm in that, then >> maybe it'd be the most flexible... > > http://dep.debian.net/deps/dep14/ > > Various tools already respect this convention so it's not really just a > suggestion anymore, and I can't see a good reason for breaking it.
Indeed. I didn't know that until yesterday when I wanted to have a '~' in an upstream version and generate a tarball with gbp from a Git tag on that version, but gbp automatically replaces '_' and ':' in Git tags by '~' and '%' respectively[0]. Thanks for the link, didn't know about that DEP though... -- Arnaud Fontaine [0] https://github.com/directhex/git-buildpackage/commit/3c6bbd0f4992f8da91693494f1a8980a4152e564
signature.asc
Description: PGP signature
