[Lazarus] Conflicting packages in fixes_0_9_30

[Mattias Gaertner]

On Sat, 18 Jun 2011 12:57:29 +0100
Hans-Peter Diettrich <DrDiettrich1 at aol.com> wrote:

>[...]
> > In 0.9.30 there were some test packages 'LCLBase' and 'LCL1' for testing 
> > the build modes and some other features. You should *not* use them 
> > (LCLBase, LCL1) in your projects and you must not install them.
> > 
> > In 0.9.31 the package LCL became a normal package and was split into LCL 
> > and LCLBase.
> 
> And this is the origin of my problem: I had created a test project with 
> Lazarus trunk, and then tested it also with the 0.9.30 branch, where 
> LCLBase is not required.
> 
> It's a bit confusing when 0.9.30 comes with a LCLBase package for "some 
> features", while trunk adds an obviously very different package of the 
> same name to all projects. Without that name clash the error message 
> simply had stated "package not found", and it had been much clearer that 
> the bug sits in the project, not in the installation.

It's the same LCLBase. Just improved. Of course if you go from
0.9.31 down to 0.9.30, then it's the opposite - the LCLBase became
worst.

 
> So much about "write once, compile everywhere" :-(

The problem is, that in 0.9.30 the LCL was using some Makefile and IDE
magic.
Anyway, adding LCLBase as dependency is not useful. The IDE now uses
the LCL instead.
Please test.


Mattias