I don't think, that would work. There is a lot of packages relying exactly on version 1.0.22. Of course I could change the version string to make the new version masquerade as the old one, but I'm afraid to cause serious problems by this.
I don't think, that would work. There is a lot of packages relying exactly on version 1.0.22. Of course I could change the version string to make the new version masquerade as the old one, but I'm afraid to cause serious problems by this.
|