Josh, Feel free to re-package it. My only warning is that the supporting CO files (DOS100/DOS200/DOSNEC/SAR100/SAR200) and the dictionary (mcomm.dic) need to be in the same directory as the python code. This allows UR-II and SARDINE to load those files regardless of what directory you are browsing.
Kurt On Fri, Oct 16, 2020, at 9:49 AM, Joshua O'Keefe wrote: > On Oct 16, 2020, at 9:41 AM, Greg Swallow <gswal...@mchsi.com> wrote: > > "ar x mComm_1.2_all,deb" ends up at another command prompt. From what I can > > tell does not “open” the .deb file > > Hi Greg, > > A .deb file is an archive (similar in concept to a ZIP file) that contains a > couple of tar files. Running the "ar" command should result in at least two > files being created: control.tar.gz and data.tar.gz. If that doesn't happen, > you may have a bad copy of the deb file (although I'd expect the command to > make noise). > > Note that as a very old school UNIX command, "ar" will produce no visible > indicator that it succeeded and will emit messages only if it fails. Just > look in the directory and I hope you will find the tar files there. Within > the data tar file is the script itself and the attendant bits. > > I hope this helps! If Kurt gives his consent, I could post a repackaged > version that is slightly easier to install on non-Debian systems.
