On Wed, 25 Jul 2018 18:20:52 -0700, Jonathan Nieder wrote: > > In fact, there is: the Repository field in debian/upstream/metadata.[1] > > Neat! > > I would have expected to find this information in debian/copyright. The > Source field there sometimes names an upstream VCS but isn't required to > do so; I'd be in favor of some tightening of the requirements in > copyright-format based on how packages in the archive have been using > the field (for example, encouraging a list of lines each of which has > the same format as Vcs-* fields).
Just sharing my experience (pkg-perl again :)): We're tracking upstream VCS (well, just Git) locations since about 4 years. The default is to record them in debian/upstream/metadata. [0] That was based on the simple fact that there was a specification for it (with the Repository: key) and that writing and reading YAML is trivial. A group of packages uses the Source field in debian/copyright, which in my experience is a bit of a pain since parsing out the Git location from a list of URLs in a multiline field is not trivial. Summary: I'm a happy consumer of upstream git locations, I'm all for standardizing, keeping debian/upstream/metadata is easiest for us; if we decide on anything else, be it d/control or d/copyright, then I very much suggest to use a new single unambiguous field for the information. Cheers, gregor [0] And we've built tools around it, as dpt subcommands. -- .''`. https://info.comodo.priv.at -- Debian Developer https://www.debian.org : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D 85FA BB3A 6801 8649 AA06 `. `' Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe `- NP: Beny More: Que Bueno Baila Usted
signature.asc
Description: Digital Signature
