Re: [fossil-users] Howto construct a download url for the latest file in a repository?
The zip file is for the entire checkout - any way to download the latest version of a single file without referring to a particular version with a sha1? If not how can I deduce the sha1 of the latest commit of a given file based on parsing the output of fossil shell commands? On 12 March 2011 22:57, Richard Hipp d...@sqlite.org wrote: Hi Richard - the above style url, or http://.../raw/libOPN_IRC.livecode?name=tip leads to an http download of the manifest file, not that actual file the manifest refers to. Any other thoughts? http://.../zip/checkout.zip?name=trunk ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Howto construct a download url for the latest file in a repository?
To get the trunk version of file webui.wiki, you can use (in bash): $ fossil artifact `fossil artifact $(fossil info trunk | grep uuid | tr -s | cut -d -f2) | grep webui.wiki | cut -d -f3` What it does is: Get uuid of the last trunk commit. Then get the manifest for that commit. Then check the uuid of the file we are interested in. Then get that file. Note that this might break in case of delta manifests. That will require more work, but the principle will stay the same. Mark On Sun, Mar 13, 2011 at 1:24 PM, David Bovill da...@architex.tv wrote: The zip file is for the entire checkout - any way to download the latest version of a single file without referring to a particular version with a sha1? If not how can I deduce the sha1 of the latest commit of a given file based on parsing the output of fossil shell commands? On 12 March 2011 22:57, Richard Hipp d...@sqlite.org wrote: Hi Richard - the above style url, or http://.../raw/libOPN_IRC.livecode?name=tip leads to an http download of the manifest file, not that actual file the manifest refers to. Any other thoughts? http://.../zip/checkout.zip?name=trunk ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] Howto construct a download url for the latest file in a repository?
Is there a syntax for constructing a url which would directly download a file from the repository? Looking at the way the web site is constructed it looks like there are only direct urls to a particular artifact - I want to use a url to link to the latest version of the file, not a particular artifact. As an example I have set up a multiple repository we site, and the url to a particular version of a file looks like this: - http://... /raw/libOPN_IRC.livecode?name=bf6a5a5751878cf242e2733656554ec131f3657c If I now update this file, then the above url will no longer point to the http download url for the latest file. Is there a way to construct this - or will I have to write a custom cgi that calls fossil via the command line? ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Howto construct a download url for the latest file in a repository?
On 12 March 2011 17:37, Richard Hipp d...@sqlite.org wrote: In the name=NAME part of the URL, the NAME does not have to be a SHA1 hash. It can be any of the forms described at http://www.fossil-scm.org/fossil/doc/trunk/www/checkin_names.wiki such as trunk. So perhaps you could use: http://.../raw/libOPN_IRC.livecode?name=trunk Hi Richard - the above style url, or http://.../raw/libOPN_IRC.livecode?name=tip leads to an http download of the manifest file, not that actual file the manifest refers to. Any other thoughts? ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Howto construct a download url for the latest file in a repository?
On Sat, Mar 12, 2011 at 5:21 PM, David Bovill da...@architex.tv wrote: On 12 March 2011 17:37, Richard Hipp d...@sqlite.org wrote: In the name=NAME part of the URL, the NAME does not have to be a SHA1 hash. It can be any of the forms described at http://www.fossil-scm.org/fossil/doc/trunk/www/checkin_names.wiki such as trunk. So perhaps you could use: http://.../raw/libOPN_IRC.livecode?name=trunk Hi Richard - the above style url, or http://.../raw/libOPN_IRC.livecode?name=tip leads to an http download of the manifest file, not that actual file the manifest refers to. Any other thoughts? http://.../zip/checkout.zip?name=trunk ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users -- D. Richard Hipp d...@sqlite.org ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
