Hello, On sekmadienis 13 Gruodis 2009 12:50:44 Jari Aalto wrote: > The "_" as a replacement is not ideal becaus it is too generic. It's > better to select a special character most likely not used for anything > else. A suggestion: > > epoch(:) => # (I agree with Sean) > tilde(~) => % > > You can test allowable tag formats with: > > git check-ref-format debian/1.5%20091201 > > See git-check-ref-format(1) manual page
I don't agree that replacement should be something very uncommon. It will simply distract people and look odd. On the contrary, ~ is typically used in place of upstream '-', e.g. 1.2.3-beta1 -> 1.2.3~beta1. '-' is also very similar to '~' visually. Only the last - is special in debian version so I don't see why already very common symbol in versions '.' was chosen as the replacement for '~'. I doubt that there are cases when '~' is actually used to replace upstream '.'. As for sed etc., solution is pretty simple: just make tag annotation parseable and extract real version from there. I dislike how current git-buildpackage wastes tag annotation for obvious words like "Tagging" or "Debian release". This info is already obvious from the tag itself (upstream/ or debian/ namespace). Currently I use "complete unmangled version/distribution" (e.g. 1.2.3-1/unstable) format for annotations and I'm very happy with how it looks visually. This way tags give a very good and useful history how and when packages were uploaded to debian archive. Due to these issues, git-buildpackage tagging helper is a no-go for me. -- Modestas Vainius <[email protected]>
signature.asc
Description: This is a digitally signed message part.
