On Mon, Nov 30, 2009 at 8:17 PM, Ian Bicking <i...@colorstudy.com> wrote: > On Sun, Nov 22, 2009 at 4:52 PM, Tarek Ziadé <ziade.ta...@gmail.com> wrote: >> >> As suggested in Catalog-SIG by some people, I would like to propose >> the addition of three more fields for 1.2: >> >> "Repository-URL" >> A string containing the URL for the package's repository. >> Example: >> http://svn.python.org/projects/python/trunk/ > > I like this in concept, but it's a bit vague as just a URL. What kind of > repository is it? Sniffing is possible, but doesn't work that well. For > pip I require something like hg+http://... (with exceptions for schemes that > are self-describing, like svn: and git:).
I didn't think that Pip would use this field to do some automatic process, I think the use case was to simply display that url at PyPI. OTHO, Repository-Browse-URL already plays that role, so it would be interesting to provide in "Repository-URL", urls that could be processed by installers. Do you have a particular use case in mind ? > It's also unclear whether it should point to the trunk, a branch, or a tag > (related to the release). As a URL that's only even possible for svn, as > git/hg/bzr all point to the repository and URLs can't point to revisions, > tags, etc. (pip has some extensions to the URL format to accommodate these, > but they aren't formally defined at this time). Good point. I think this would end up being the trunk/default path *or* the root of their repository, because I doubt developers will update this field for every release they have. And, as you said, in mercurial for instance, we would need to "hg up some_tag" to have a similar feature than svn branches. So at the end, maybe we could just keep "Repository-Browse-URL" and drop the other one unless we can come up with some use cases for automatic processing of the url. Tarek. _______________________________________________ Distutils-SIG maillist - Distutils-SIG@python.org http://mail.python.org/mailman/listinfo/distutils-sig
