Manoj Srivastava <sriva...@debian.org> writes: > On Tue, Jun 23 2009, Jonathan Yu wrote:
>> For me it just seems odd to add fields to d/control that aren't in >> policy, though your explanation makes sense to me. > Policy should be minimalistic. Is there any compelling reason > to pull this into policy? Well, from my perspective, the main reason why I'd like to have it in Policy is that people have started making errors in the fields (putting the Vcs-Browser URL in Vcs-Svn, etc.), and it would be nice to have a clear specification against which one can write Lintian checks. That specification could, of course, be in the devref, but it's nice to put established specifications in Policy precisely because they then don't change much. Also, as mentioned, we had real trouble finding documentation for what was supposed to go into the Vcs-Mtn field, since Monotone doesn't use URLs. -- Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/> -- To UNSUBSCRIBE, email to debian-policy-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
