You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current version of c-lime is lime-1.3.2. It can be downloaded as lime-1.3.2.tar.gz.
which refers to a tag back to 2009. However, the repository has evolved since then and also serious bugs that prevented using lime with large configurations where fixed. I naively thought that v1.3.2 was the most recent stable one and hence started debugging myself the lime_pack source code once triggering that int overflow and I would have never imagined to find on the master much newer code. I then also noticed that the "Download TAR Ball" button on the project webpage actually leads the user to get a tarball of the master branch at the moment of download, which is in most of the cases not a tagged release.
Always in the Code releases section, it is also to read
but also there only very old releases are to be found.
Do you plan to tidy up the webpage in the next future and draft a new release, which would be probably very useful? I saw that there is some work going on on the feature/cmake branch. Does this means that you are planning to restructure the codebase to a cmake approach?
I opened this Issue just to leave some trace and possibly avoid confusion to other users in the community.
The text was updated successfully, but these errors were encountered:
On this project webpage in the Code releases section, it is stated that
which refers to a tag back to 2009. However, the repository has evolved since then and also serious bugs that prevented using lime with large configurations where fixed. I naively thought that
v1.3.2
was the most recent stable one and hence started debugging myself thelime_pack
source code once triggering thatint
overflow and I would have never imagined to find on the master much newer code. I then also noticed that the "Download TAR Ball" button on the project webpage actually leads the user to get a tarball of themaster
branch at the moment of download, which is in most of the cases not a tagged release.Always in the Code releases section, it is also to read
but also there only very old releases are to be found.
Do you plan to tidy up the webpage in the next future and draft a new release, which would be probably very useful? I saw that there is some work going on on the
feature/cmake
branch. Does this means that you are planning to restructure the codebase to acmake
approach?I opened this Issue just to leave some trace and possibly avoid confusion to other users in the community.
The text was updated successfully, but these errors were encountered: