[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#682282: Please document syntax of Vcs-Cvs field



Package: debian-policy
Version: 3.9.3.1
Severity: wishlist
Control: block -1 by 654958
X-Debbugs-Cc: "Bernhard R. Link" <brlink@debian.org>, cvs@packages.debian.org

Hi,

Bernhard R. Link wrote[1]:

>> +		<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.

Thanks.  Filing so it's not forgetten.  (If someone wants to prepare
an exact paragraph that can be cut-and-pasted into policy, all the
better, of course.)

Hope that helps,
Jonathan

[1] http://bugs.debian.org/654958#134


Reply to: