Mattias Gaertner wrote:
On Tue, 11 Sep 2012 19:39:08 +0000
Mark Morgan Lloyd <[email protected]> wrote:
Plus others in fpc-devel. What we need is a "I've just committed
something to svn trunk which breaks it for 2.6.x, normal service will be
resumed shortly" button.
That would be wrong.
fpc 2.6.1 was changed, which broke Lazarus. Lazarus was adapted, so
it can not compile with older fpc 2.6.1.
Compilation with fpc 2.6.0 was not affected.
With emphasis please on my "normal service will be resumed shortly", I'm
not suggesting that the core developers gratuitously break things. I was
thinking of cases where something is changed in one or other of the
projects, and where somebody knows that this will cause problems for
minutes or hours (or, in very rare cases, days). Some sort of "health
warning" would be useful, so that people (or scripts working on their
behalf) know that it's best to hold off any updates to their local copy
until the situation is resolved.
--
Mark Morgan Lloyd
markMLl .AT. telemetry.co .DOT. uk
[Opinions above are the author's, not those of his employers or colleagues]
--
_______________________________________________
Lazarus mailing list
[email protected]
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
