|Message: Re: md5 hashes: request for rmd160 or sha256||Not Logged In (login)|
Click on the Forum title, e.g. on the "Forums by Category" page, to read a sequence of postings to the Forum and its threads all in one page. If you are only interested in one thread or the thread following a specific posting, click the thread or the posting, which takes you to a smaller page, which contains only the part you are interested in and may be easier to navigate.
Messages are "chained" if there are only replies at the first level, i.e. 1/1.html, 1/1/1.html etc. In case of "chained" messages the message number is replaced by the icon and there is no indentation.
Inline: Display the subject line only or also the text of the posting(s); for the choice "All" the "Outline" choices are switched off.
|1||0||1||no text / full text of posting|
|2||1||All||text for level 1 only / text for All postings|
Outline: Choose the depth of the posting thread, successive toggle controls provide increasing detail.
|1||2||1||2 levels / 1 level (original posting)|
|2||3||2||3 levels / 2 levels|
|3||3||All||3 levels / all levels (all postings)|
On Tue, 02 Jul 2013 16:10:56 GMT, Mojca Miklavec wrote: > Thank you. This probably means that you need to wait until you decide to > support just CMake 2.8.10/2.8.11 or newer, judging from this: > https://github.com/Kitware/CMake/commit/beb8a8309bc0ce08e4884a59329607ac09c322ac > and the changelog mentioning "ExternalData: Add support for SHA 1 and 2 > hash algorithms" in Release notes for 2.8.11?
To clarify - we won't fully support sha256/rmd160 in the Geant4 CMake scripts at the moment because of the version support requirements (If there is time, I will look at enabling sha256 checking when the running CMake supports it). However, we will look at publishing the hashes on the download page.
> > I'm guessing though that you're downloading and installing the datasets > > as a separate port or custom step in the geant4 port? > > Yes. I try to find the data (name, version, checksum), copy it and > install it separately. In the way that MacPorts work that makes more > sense and is easier to control.
Publishing the hashes should solve this as you'll be able to take them direct from the website.
|Inline Depth:||Outline Depth:||Add message:|