Hi Simon,
Simon Kainz wrote:
> Currently i choose the VCS tool to use not by the URL scheme but by
> the field name: VCS-Git, VCS-Svn, ... This works currently only for
> d/control file. In upstream metadata, the Repository: field gives no
> indication which VCS was used.
*nod* Sounds sane.
> So it's quite impossible to find the "correct" VCS, because at least
> GIT, SVN and HG (and some others) may also use HTTP(S) for transport.
>
> I currently implemented detection of non-HTTP based URL schemas with
> the follwing implications:
>
> git:// and svn:// Urls are checked usign the appropriate tool,
You may also want to generally exclude all URLs which have
"svn+ssh://" or "ssh://" as protocol. (Not sure if "git+ssh://" also
exists.)
> all other HTTP(S) based URLS with no indication as what VCS they
> might be using, are simply checked for basic availability via HTTP.
> This means only reporting HTTP 403, 404, 500 and some more HTTP
> errors.
Which is fine IMHO. That will find at least (re)moved repositories
(and did in the past), but now with less false positives -- which is
definitely an improvement.
> I would prefer doing a check with the appropriate tool, but I think
> this is currently better than wildly guessing which VCS might have
> been used by trying different permutations of the Repository URL,
> which might give even more unreliable results.
Yes. There are likely a few heuristics, but then again they're still
heuristics and may be wrong.
> This is implemented in duck 0.4, to be uploaded soon.
Yay, thanks.
Regards, Axel
--
,''`. | Axel Beckert <[email protected]>, http://people.debian.org/~abe/
: :' : | Debian Developer, ftp.ch.debian.org Admin
`. `' | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE
`- | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
