I was wondering what is planned regarding packages available on SqueakSource and Pharo. More and more packages can't load in Pharo and it gets more and more frustrating not being able to load anything without having to add/modify methods/classes all over the place so those packages can load properly in Pharo. Are we looking at a Pharo-only kind of SqueakSource in the future ? Besides, having to handle platform specific (i.e. Pharo vs Squeak) for every package is adding more complexity than what is needed. I know backward compatibility was thrown away from the start to avoid compromises in Pharo but how do we take care of the fact that as each day passes, less and less stuff from SqueakSource is usable in Pharo ? tia  ----------------- Benoit St-Jean Yahoo! Messenger: bstjean A standpoint is an intellectual horizon of radius zero. (Albert Einstein)