Hello,
John Palmieri recently helped me with a ticket (#16350) where the
> spkg-install
> of a package was changed but that was not enough to trigger the necessary
> rebuild. That could be accomplished by adding '.p0' to the
> package-version.txt
> because patch level changes don't change the ac
John Palmieri recently helped me with a ticket (#16350) where the
spkg-install
of a package was changed but that was not enough to trigger the necessary
rebuild. That could be accomplished by adding '.p0' to the
package-version.txt
because patch level changes don't change the actual version string
On Tuesday, May 27, 2014 6:02:20 AM UTC+2, Ralf Stephan wrote:
>
> I have reread this thread and I'm asking myself if the ecl upgrade
> shouldn't have simply bumped the package-version.txt of maxima at
> patchlevel, thus forcing a rebuild. I mean the author of that ticket surely
> had the same
I have reread this thread and I'm asking myself if the ecl upgrade
shouldn't have simply bumped the package-version.txt of maxima at
patchlevel, thus forcing a rebuild. I mean the author of that ticket surely
had the same fail when testing, and the reviewer too?
Please tell what I'm missing.
Reg
You have my attention. We can of course wait with any future releases until
somebody fixes this.
In an ideal world we would have reliable library versioning, so you
wouldn't need to rebuild maxima UNLESS the ecl library version changes in
an incompatible way (which can be read off from the name
