On Fri, Apr 03, 2009 at 10:04:21AM +1100, Ben Finney wrote:
> Raphael Geissert <atomo64+deb...@gmail.com> writes:
>
> > I planned to add support for svn in version 4 watch files (it would
> > be a matter of svn info svn://domain.tld/path/to/repo and some data
> > massaging).
> >
> > But well, now that everyone is talking about it why not just tell
> > what is missing so that it can be addressed in version 4 watch
> > files?
>
> For my purposes, I would like to be able to specify “fetch from the
> VCS at $URL, getting the specific working tree referenced by
> identifier $ID” and then the rest of what uscan does for generating
> an original source archive from the working tree.
>
> That's made more complex, of course, by:
>
> * the fact that the URL doesn't necessarily indicate what VCS tool is
> needed to interact with it (just about all of them allow an HTTP URL
> for public read-only access, so that's what will commonly be used
> here)
>
> * the plethora of different concepts for mapping identifiers to
> specific working trees in different VCSen (revision-id and branches
> and tags, oh my!)
This could be possible with a set of configurable rules, akin to make.
get-recent:
svn co http://example.org/ $DIR
get-revision:
svn co -r $REV http://example.org/ $DIR
As long as you standardised the variables passed, and the location, should work.
--
Noah Slater, http://tumbolia.org/nslater
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
