[Octave-bug-tracker] [bug #51450] [octave-forge] database 2.4.2 fails to build in dev octave 4.3.0+

[Olaf Till]

Follow-up Comment #8, bug #51450 (project octave):

A fix is pushed, including a general frame to deal with simple symbol changes.
I suggest to use this frame for similar cases, it'll be published at the OF
website.

Deprecated symbols don't seem to be available long enough for my previous
strategy to work.

As for filing bugs for build failures with dev, I can't suggest a general
rule. In the packages which I maintain I think I would fix these even without
reports, but in some cases not before dev is about to become the next major
release. But your build fixes against dev for many packages are doubtless
really useful.

On the other hand, maybe a development strategy for the Windows build could be
devised in which you have more time to wait for (or produce...) build fixes of
packages against dev ...? It's only because package development normally
doesn't immediately parallel each change in Octave dev, except on Windows.

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?51450>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/