On Sat, May 17, 2008 at 10:40:53PM +0200, Pierre Habouzit wrote: > On Sat, May 17, 2008 at 05:04:56PM +0000, Manoj Srivastava wrote: > > On Sat, 17 May 2008 15:24:13 +0200, Pierre Habouzit <[EMAIL PROTECTED]> > > said: > > > > > > > (publishing my branch in a gitweb) isn't normalized, and won't > > > probably ever be, or not under this form. > > > > Don't you think that Vcs-Browse and Vcs-$SCN headers are > > normalized ways for telling end users where to get the development > > sources from? > > For devel sources yes. Sadly, this won't give you the straight URL to > what upstream are interested in. > > > We might want to see if we should shipt the VCS-* headers > > in the Packages file, but I thought we are trying to standardize > > publication of DVCS repositories in Debian now. > > Well, that's not needed, that could be really easily used in a > patches.d.o service like Vincent is asking for. Though even with VCS-* > headers, it's still hard to _automatically_ present things coherently > enough for automated tools to do some useful reports. OTOH such tools > could be written for each VCS< there aren't _that_ many of them (I mean, > compared to the number of bug-trackers out there, bts-link showed such a > task is doable). but again, even grokking the VCS isn't enough, you'll > have to know where the maintainer put things in the first place. ANd > here, grokking git isn't enough. *I* don't even use the same name for > all my packages, I don't expect it to be more coherent for _different_ > packagers. > > All in all, pointing to VCSes is just making things harder, because > you fight against direct product of VCSes, workflows, and almost > packages. And no tool is really gonna sort that out. OTOH, if we _do_ > mandate people to one way or another serialize their patches in the > source format, with comments and all that stuff, then it _IS_ a good > thing, because that's the kind of things that can be grokked by tools > trivially. And for that, the v3 format goes in the proper direction.
s/the v3 format/the v3 quilt format/ Mike -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
