Avoid re-fetching binaries when they exist

[vacantron]

Now, we fetch the SHA1 first and verify the binaries. Only if the check fails, the download begins.

[jserv]

Improve git commit messages.

If you tend to trigger tests, specify "WIP:" in the subject.

[ChinYikMing]

Rather than checking for the existence of prebuilt executable filenames, I prefer calculating and comparing their hash values with pre-calculated ones. For verifying the hash of a file or directory, see the verify function in "mk/external.mk".

rv32emu/mk/external.mk

Line 47 in abb1135

define verify

[ChinYikMing]

Enhance the git commit message by providing more details, specifically explaining how the SHA1 value is handled.

[ChinYikMing]

Is there any relationship between the 'sha1sums.csv' files in this link and this link and this commit?

If not, they can be removed from the rv32emu-prebuilt repo to keep it clean.

[vacantron]

Is there any relationship between the 'sha1sums.csv' files in this link and this link and this commit?

If not, they can be removed from the rv32emu-prebuilt repo to keep it clean.

rv32emu-prebuilt now only releases the tarball of the prebuilt binaries, and all other files in the repository will not be updated in the future.

[ChinYikMing]

Is there any relationship between the 'sha1sums.csv' files in this link and this link and this commit?
If not, they can be removed from the rv32emu-prebuilt repo to keep it clean.

rv32emu-prebuilt now only releases the tarball of the prebuilt binaries, and all other files in the repository will not be updated in the future.

I’m still confused about file suffixes related to CSV. Could you please provide more details?

[vacantron]

I’m still confused about file suffixes related to CSV. Could you please provide more details?

The contents of *.csv files are copied from the output of sha1sum and are changed to comma-separated manually (the released sha1sum-* are still whitespace separated).

[ChinYikMing]

I’m still confused about file suffixes related to CSV. Could you please provide more details?

The contents of *.csv files are copied from the output of sha1sum and are changed to comma-separated manually (the released sha1sum-* are still whitespace separated).

So, are the *.csv files primarily used to make comparisons easier to view compared to the space-separated sha1sum-* files?

[vacantron]

So, are the *.csv files primarily used to make comparisons easier to view compared to the space-separated sha1sum-* files?

I think both of them are the same with awk command. The only difference is the separating character needs to be specified when processing CSV files.

Or, do you care about the sha1sum-* files without suffix might be confused with the prebuilt binaries?

[ChinYikMing]

So, are the *.csv files primarily used to make comparisons easier to view compared to the space-separated sha1sum-* files?

I think both of them are the same with awk command. The only difference is the separating character needs to be specified when processing CSV files.

Or, do you care about the sha1sum-* files without suffix might be confused with the prebuilt binaries?

I was wondering, since we have the space-separated sha1sum-* files, would the *.csv files still be necessary?

[vacantron]

I was wondering, since we have the space-separated sha1sum-* files, would the *.csv files still be necessary?

No, but any file in rv32emu-prebuilt won't be updated since it is only for the purpose of releasing prebuilt binaries. We only fetch the files from the RELEASE page.

Or, we can simply clear the repository, but not in this pull request.

[ChinYikMing]

I was wondering, since we have the space-separated sha1sum-* files, would the *.csv files still be necessary?

No, but any file in rv32emu-prebuilt won't be updated since it is only for the purpose of releasing prebuilt binaries. We only fetch the files from the RELEASE page.

Or, we can simply clear the repository, but not in this pull request.

Agree. From my perspective, the *.csv files can be a bit confusing in terms of maintainability, especially since the useful ones are available on the RELEASE page, as you mentioned.

[ChinYikMing]

Now, LGTM.