Release a new version

[ryandesign]

yorick 2.2.04 doesn't build with llvm.org clang 18:

graph.c:4098:17: error: parameter 'argc' was not declared, defaults to 'int'; ISO C99 and later do not support implicit int [-Wimplicit-int]
 4098 | Y_current_mouse(argc)
      |                 ^
 4099 | {
graph.c:4098:1: warning: a function definition without a prototype is deprecated in all versions of C and is not supported in C2x [-Wdeprecated-non-prototype]
 4098 | Y_current_mouse(argc)
      | ^

This bug was fixed in 2018 in 83d5218 but there has not been a new release since then.

Please release a new version so that everyone who packages your software does not have to independently research how to fix this issue and other issues that you've already fixed in the nine years since your last release.

[dhmunro]

Yorick was abandoned nearly ten years ago. There have been a few bug fixes for legacy users at LLNL and for yeti since then, but 2.2.04 is the final version. You should switch to python/numpy/scipy as soon as possible; certainly it is a serious mistake to write new yorick interpreted code, as inevitably yorick will eventually fail to build on more and more systems. As a stopgap measure, you can use the LLNL/pyorick repo to incrementally migrate to python.

That said, I don't really understand the problem you are having. What do you mean by "release"? Do you simply want a new version number? If so, why? Isn't your packaging system set to grab the latest source from this LLNL/yorick repo, or are you building from the old y_2_2_04 tag instead of from the latest commit? Why are you not getting the latest "2.2.04" in the first place? If the problem is that you are getting your source from somewhere other than this LLNL/yorick repo, there isn't much I can do about that. I don't know that there is anyone to update the packages for various distros (e.g.- Debian), even if the version number were bumped to, say, 2.2.05 - I believe there is a bunch of manual work by the "maintainer" of the package for each distro that would still have to be done even if the version number here changes. Since that's the case, it would be better if those packages separately added a new subversion number if that is required for some particular case.

In any event, I don't believe that incrementing the version number of this repo will by itself fix whatever problem you are having. Yorick died at age 2.2.04, and I really have no desire to change the date on its gravestone.