On 11/22/17, Warren Young <[email protected]> wrote:
>
> 1. Visit https://example.com
> 2. Click Timeline (and how would my users know to do that?)
> 3. Click checkin ID.
> 4. Find and click Tarball link
> 5. Unpack the tarball
>
> Then they must do all 5 steps again every time there is a new version they
> want,

Maybe this is just an unfortunate example.  You do know that you can
download a specific version using a single wget or curl command,
right?  For example:

     curl 'https://www.sqlite.org/src/tarball?uuid=trunk' -o sqlite3.tar.gz

which I copied from line 25 of the Dockerfile for OSSFuzz at
https://github.com/google/oss-fuzz/blob/master/projects/sqlite3/Dockerfile

That line allows OSSFuzz to download the latest trunk check-in of
SQLite once per day and run it through OSSFuzz looking for errors.

You are right, though, that this is not obvious to most developers and
you will normally need to hand-construct some URLs to show to people.
I had to show this URL to the OSSFuzz developers at Google.  Prior to
that, they were doing an "apt-get install fossil" followed by a
"fossil clone" and "fossil open" - a combination which broke when we
moved to Fossil 2.0 and Debian was slow to update.

-- 
D. Richard Hipp
[email protected]
_______________________________________________
fossil-users mailing list
[email protected]
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Reply via email to