control: tag -1 +moreinfo Hello Iain, On Wed 25 Jul 2018 at 05:14PM +0100, Iain Lane wrote: > Some tools, like git-buildpackage, can support merging an upstream's > version history into Debian packaging repositories. This enables more > rich usage of (D)VCS when packaging - for example `git blame' works > properly. > > Currently there's no canonical place to specify where upstream's VCS is > located so people have to set this up manually themselves. If there were > such a place, it would be possible for tools like `gbp clone' to > configure the VCS to know about the upstream history when checking out a > packaging repository. In fact, there is: the Repository field in debian/upstream/metadata.[1] > The request here is to ask whether this would be suitable for > debian/control, along the lines of the Vcs-* fields specified in 5.6.26 > and the Homepage field in 5.6.23. > > If so, I'd be happy to propose wording for policy. I'm not set on any > particular name, so please feel free to weigh in on that if you'd like. Even if we did want to add this to d/control files, we would want to see it already used in d/control files in the archive before documenting that in Policy. [1] https://wiki.debian.org/UpstreamMetadata -- Sean Whitton
Attachment:
signature.asc
Description: PGP signature