What I know is this: early in the summer, when I was trying to upgrade from Pharo 1.2 to a modern version of Pharo, and gain simple DB connectivity (via glorp), I had a difficult time getting the few packages I needed to all play well together. My needs were simple: Pier for the seaside and magritte, and glorp, and Fuel. I found that I could only work with a very lean image to avoid conflicts: raw-release + pier3 + glorp + opendbx + fuel. Now I have a stable image, and I won't change a thing for a year... or until I hear that 2.0 is stable.

Magritte3 moved the xxxDescription methods to the instance side, and it uses pragmas, so the name matters less. (Not at all? i don't recall.) Overall, it was an improvement in the name space and so I am glad I spent the couple of days learning the new tools and converting/upgrading.

You might be hitting the same namespace problems that I hit related to Magritte3. The problem is #description ... -- i forget the details.

On Fri, Oct 5, 2012 at 2:11 AM, Damir Majer <damir@majcon.de> wrote:

Hi Cam, hi Mariano,

thanks for your replies.
As I understand, it seem´s that Pier2 is not stable (ready?) for the new
Pharo1.4 because of the OmniBrowser Dependencies.

So I guess, that I have to use Pier3 with the latest Pharo1.4/2.0 to get an
stable version of Pier?

Cheers,
Damir