Bug#654958: debian-policy: Document VCS fields.
Jonathan Nieder <jrnieder@gmail.com> writes:
> Russ Allbery wrote:
>> Also, for a Git repository, what do you do if the Debian packaging isn't
>> on the master branch? For example, for packages for which I'm also
>> upstream, I do upstream development on the master branch and Debian
>> packaging on a separate debian branch.
> I wonder if something like
> Vcs-Git: git://git.eyrie.org/kerberos/webauth.git squeeze
> could be made to work.
My understanding was that the debcheckout developers were not enthused
about adding a syntax that Git upstream didn't support, but I think that's
the only solution that anyone's come up with so far.
On the other hand, it is kind of silly for them to be in such widespread
use without Policy saying anything about them. Maybe we should just
document them as they are and be explicit about the limitations, saying
things like:
The information in the Vcs-* header should be sufficient to locate the
repository used for packaging and access it anonymously. It may or
may not be the branch used for packaging any specific version of the
package, and the packaging is not necessarily on the default branch.
Additional investigation is often required to find the part of the
repository used for current development or for any particular version
of the package.
If, over time, debcheckout and our package metadata starts making more
explicit guarantees, we can always tighten the language later, but the
above reflects the current state of the archive.
--
Russ Allbery (rra@debian.org) <http://www.eyrie.org/~eagle/>
Reply to: