Dušan Baran

@microsoft-github-policy-service agree company="TileDB"

For our use case only `libfaketime.so` is needed and I prefer using CMake. I hope it is not an issue :) .

I reworked this PR to use Make instead of CMake but right now it fails due to I assume incorrect working directory, is there a chance to change it?: ```...

I believe that **backwards_compatibility** tests not passing is not an issue of this PR

> * please run the workflow here against a prior release (eg 2.20.0-rc1 is fine) and compare the bundles with existing workflow to this one, in order to make sure...

I have no problem also adding a json format, however, do you really need release build outside cmake? I can read JSON from CMAKE without any issues since I can...

Ok so my next plan is to: 1. Create CSV file of all releases + source 2. Change sha1 to sha256 if its ok with everyone (because it might create...

This might be a format that could be compatible with both R and CMake: ``` (base) dudoslav@beetle:~$ cat rellist.csv os,arch,url,sha,noavx2 LINUX,X86_64,https://SOMEURL.com,da39a3ee5e6b4b0d3255bfef95601890afd80709, LINUX,X86_64,https://SOMEURL.com,da39a3ee5e6b4b0d3255bfef95601890afd80709,NOAVX2 WINDOWS,X86_64,https://SOMEURL.com,da39a3ee5e6b4b0d3255bfef95601890afd80709, ```

@teo-tsirpanis I really like your suggestion, but there is a requirement from the R team for a format that could be easily included without dependencies. So JSON is somewhat out...

Also, I am still not sure where to put this download logic, since it will not change between releases. Only the rellist changes. Maybe if I would hardcode the latest...