Binaries Upgrade

[privateOmega]

Hey @jmhmd,

Thanks for this library.

I am planning to use this in a production setup and I was wondering if we could upgrade the binaries to latest version 3.6.6, as in do you anticipate any issues?

I noticed that you had stuck with 3.6.0 for mac and 3.6.2 for linux and windows which gives me the feeling that you must have done it for good reason. It would be great if you could post your reasoning here? I would happily raise a PR against this repo, for replacing the binaries and all that.

I have already forked your repo and exposed some other methods like pdf2dcm etc, but havent raised a PR since I hadn't worked on the matchers part, but hopefully will do it soon.

[jmhmd]

Hi, glad you have found this useful.

The currently used versions were the latest prebuilt binaries I could find for each platform at the time I started this library. Since the library depends on parsing log output from dcmtk, it is potentially more risky to change versions as the log parsing might break if the log format changes at all between versions. Most likely a change in log format would not be considered a breaking change in dcmtk so might not be mentioned in release notes. There are some tests which will hopefully catch any major issues but not guaranteed. The versions used now have all the functionality I needed so I never bothered to upgrade.

Feel free to upgrade and test, hopefully the logging format is the same and everything will work as expected!