Hello all,
The tarballs at
/g/d-rats/files/D-Rats is designed as a PIP installable tarball.
Python installer maintainers have deprecated the storage of the additional data that D-Rats stores in the its library directories.
Their feeling is that should be handled by an operating system packaging system, like RPMs or Debian packages, etc.
I did a lot of work to create MSI files and Debian packaging for the LZHUF project. I was not able to create packages for Raspbian distributions.
Someone familiar with creating RPMs or Debian packaging should be able to work out how to convert the pip installable tarball into a one of those packages.
It is just that I just am not going to have the cycles to be creating that type of packaging for D-Rats on Linux at this time, and be able to get anything else done.
For msys2, I have found that there are several articles that give instructions on how to create a "embedded" msys2 setup in their WIKI.
One of them should be usable. Once it has been determined how to setup one of those environments and then add the PyPi, lzhuf and d-Rats to that environment, the steps for creating a MSI files as was done in the lzhuf project could be used to create a D-Rats MSI file.
But all of that still will take a lot of work and time, and for now, the easiest way to run D-Rats is probably to run it from a checkout of a cloned repository. The original D-Rats was supplied as a tarball, and it was community help that expanded it to be a Windows executable package, so running from a cloned checkout is almost going back to a full circle.
73,
-John
