Ian Jackson <ijack...@chiark.greenend.org.uk> writes: > I wrote: > >> Hrm. Some of the things that we envisage in the future will rely on >> being able to find the maintainer view tag, as well as the dgit view >> one.
BTW in case it matters, I don't think I care whether one ends up with both the default tag that's currently being created (the 'debian/1.2.3' thing), as well as the custom one, but then again DEP-14 does include the idea of not including the distro bit in the tag if one is really the upstream, so erm, well doing both might really be wrong. > So I guess this would be a config option, where you specify a template > (with a %s in it I guess) for the tag you would like dgit to make. If it's supposed to be possible to do the thing where one can ignore the epoch in a version, then I guess it's more than a %s that's required (assuming that the string that's going into the %s was supposed to be the DEP-14 munged version from the changelog). One possibility would be to allow one to specify a command, that is given the current default tag value on STDIN and is expected to spit out the tag to use on STDOUT? So one might have: dgit-distro.debian.dgit-tag-filter="sed -ne 's,^debian/1%,,p'" then one could throw an error if the output is empty (which would be the case here if something unexpected happened, like the epoch being set to 2). Of course, if it's obvious what people might want to do with this, one could perhaps have some sort of PRETTY FORMAT style substitution where e.g. %v is the version, %V is the epoch-free version, %d is the distro bit, and maybe %e is the epoch -- no idea if that's all one needs though. > It should probably be a distro specific one (ie an "access" config > key) so you could do this iff you were uploading to Debian bug skip it > when uploading to Ubuntu, or whatever. > > Presumably it should do this iff > 1. That config option is set > AND > 2. The version number has no Debian revision > ? Seems reasonable. > If the config key is set and the version has a Debian revision, should > it fail or simply not make the tag ? I a inclined to say "fail". Fail, I'd think, as that makes the maintainer read the docs. > And should it apply the usual Debian to git syntax transform (as per > DEP-14) ? Or should it reject version numbers that wouldn't be > unchanged under that transform ? Or what ? If using the filter idea above, I'd insist that the result is a valid tag already, or fail. > With answers to these questions I think this becomes a fairly > straightforward SMOP. Cool. Cheers, Phil. -- |)| Philip Hands [+44 (0)20 8530 9560] HANDS.COM Ltd. |-| http://www.hands.com/ http://ftp.uk.debian.org/ |(| Hugo-Klemm-Strasse 34, 21075 Hamburg, GERMANY
signature.asc
Description: PGP signature
