Re: Bug#466550: Pristine source from upstream VCS repository
Ben Finney <email@example.com> writes:
> Ben Hutchings <firstname.lastname@example.org> writes:
>> # Upstream homepage links to a file called puzzles.tar.gz which
>> # redirects to puzzles-r$version.tar.gz. uscan can't check that.
>> # However, this is a nightly snapshot numbered according to the SVN
>> # revision number, so we can extract the version number from its web
>> # view.
>> opts="filenamemangle=s/.*\?rev=(\d+).*/sgt-puzzles_$1.orig.tar.gz/,downloadurlmangle=s@.*\?rev=(\d+).*@http://www.chiark.greenend.org.uk/~sgtatham/puzzles/puzzles-r$1.tar.gz@" \
>> http://svn.tartarus.org/sgt/puzzles/ /sgt\?rev=(\d+)\&view=rev
>> OK, so it's not exactly pretty...
> It also fails in those instances where “available from a VCS” does
> not mean “available as a working tree of files via HTTP”. Some VCS
> repositories make *only* the revision data available, for various
For ffmpeg (and mplayer AFAIUI), upstream provides only revision data,
and is heavily using svn:externals, which forced me doing horrible
things like this:
Does someone manage to "port" that script to uscan? ;-)
Reinhard Tartler, KeyID 945348A4