Outdated apt package and release tag
clydeshaffer opened this issue · comments
I've had this come up as a friction point a couple of times where someone tried to build my code, got errors that I didn't, and it turned out the reason was that they installed cc65 with apt or they used the most recent build on the "releases" tab.
One example is that the signature of inflatemem() was changed and now causes an error by default when building code written for recent cc65 with the "latest release" of cc65.
Could the version number and release tag be bumped? Or is there a particular reason that it's been left alone for four years?
