Bug#654958: debian-policy: Document VCS fields.
Jonathan Nieder <jrnieder@gmail.com> writes:
> If I keep my sources in svn, should I give a URL to the toplevel of the
> repository (which is what one passes to "git svn clone -s" and allows
> access to all branches) or one particular branch?
For debcheckout to work properly, you want to specify a branch.
> If a branch, which branch, and should its content at the tip represent
> the last uploaded version or is it allowed to be ahead of, behind, or
> even unrelated to that? Should the content at the tip match the
> uploaded package, or is allowed to contain more, less, or some unrelated
> collection of files?
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've always found the Vcs-* headers a bit underspecified, or at least
limited. (I'm fairly sure the answer to my question is that debcheckout,
which is the only real consumer of the Vcs-* headers that I know of other
than statistical analysis of types of repositories, just can't handle that
case at all.)
--
Russ Allbery (rra@debian.org) <http://www.eyrie.org/~eagle/>
Reply to: