Bill Allombert <bill.allomb...@math.u-bordeaux1.fr> writes: > On Wed, Jun 24, 2009 at 04:22:48PM +1000, Ben Finney wrote: > > Jonathan Yu <jonathan.i...@gmail.com> writes: > > > > > I don't really think that each version control system should have > > > its own field, like Vcs-Mtn, Vcs-Svn, Vcs-Git etc, because it's > > > simply not very future proof in my opinion. > > > > What's the alternative? > > This one is easy: > > Vcs: git:http://git.debian.org/... > Vcs: svn:http://svn.debian.org/... > > (This means that dpkg does not have to be updated for each new VCS).
I'm unaware of this issue. I was under the impression that dpkg can simply handle fields transparently if it doesn't need to do anything with them. Why does dpkg need to be updated for each of ‘VCS-git’, ‘VCS-svn’, and so on if it doesn't actually use them? -- \ “Kissing a smoker is like licking an ashtray.” —anonymous | `\ | _o__) | Ben Finney -- To UNSUBSCRIBE, email to debian-policy-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
