Hi Paul > A retry worked. It seems to me that the failure was due to lazarus not > having been rebuild against the latest fpc in the archive. More exactly, because the installed lcl-units-* were not build using the installed FPC.
> But in Debian > I'd expect package relations to embed the knowledge to prevent this from > happening. This is generally the case except when FPC get upgraded to a new version, which is generally a transitory situation for a very short time. > > Similar to the discussion in bug 997940 about src:castle-game-engine. It is not exactly the same. Lazarus is an IDE + framework (LCL). The IDE itself can work with whatever FPC version and with many LCL versions. So in principle, one can install the IDE and have a custom FPC + LCL. One problem here is that the LCL is packaged with the IDE, and this is a issue from upstream not separating the IDE development from the framework development. I don't like the idea to enforce the dependency because in principle, the same instance of Lazarus IDE can work with FPC-2.2.0 and FPC-2.2.2 which allows a developer to have time to migrate his application broken by a FPC or LCL upgrade wile using the last IDE. I personally use this feature for a SW that is tightly linked to LCL and thus using a new Lazarus with an old LCL until upgrade is done. -- Cheers, Abou Al Montacir
signature.asc
Description: This is a digitally signed message part
