Bug#654958: debian-policy: Document VCS fields.

["Bernhard R. Link" <brlink@debian.org>]

> +	      <tag>
> +		<tt>Vcs-Arch</tt>, <tt>Vcs-Bzr</tt> (Bazaar), <tt>Vcs-Cvs</tt>,
> +		<tt>Vcs-Darcs</tt>, <tt>Vcs-Git</tt>, <tt>Vcs-Hg</tt>
> +		(Mercurial), <tt>Vcs-Mtn</tt> (Monotone), <tt>Vcs-Svn</tt>
> +		(Subversion)
> +	      </tag>
> +	      <item>
> +		<p>
> +		  The field name identifies the VCS. The field's value uses the
> +		  version control system's conventional syntax for describing
> +		  repository locations and should be sufficient to locate the
> +		  repository used for packaging. Ideally, it also locates the
> +		  branch used for development of new versions of the Debian
> +		  package.
> +		</p>
> +		<p>
> +		  In the case of Git, the value consists of a URL, optionally
> +		  followed by the word <tt>-b</tt> and the name of a branch in
> +		  the indicated repository, following the syntax of the
> +		  <tt>git clone</tt> command.  If no branch is specified, the
> +		  packaging should be on the default branch.
> +		</p>

Why only document git and not the syntax of the other fields?

cvs: a identifier suiteable for cvs -d (i.e. usually starting with :pserver:),
followed by an optional module name (seperated by a space).

I think it might also make sense to explicitly request that the fields should
describe an anonymous checkout.

        Bernhard R. Link