I think the build will become unstable with every package update...� So maybe we should update every ConfigurationOf used by pharo, and put symbolic versions into it
Guille
Absolutely not. Otto did a mistake so this caused problems. So isn't it obvious to rollback the configuration back to the point it worked.�On 25.02.2011, at 17:48, Marcus Denker wrote:On Feb 25, 2011, at 5:42 PM, laurent laffont wrote:On Fri, Feb 25, 2011 at 5:11 PM, St�phane Ducasse <stephane.ducasse@inria.fr> wrote:
Exact
On Feb 25, 2011, at 2:10 PM, Torsten Bergmann wrote:
> Markus wrote:
>> The XML package breaks the build? So let's remove it completely. Let's ship >1.2, but without all the packages that are problematic.
>
> It's not that the package is problematic - the Configs are problematic
But still can't Pharo Dev focuses on tools and not frameworks that we should load by ourselves.
Because else why not loading, cassandra, coucdb, opendbx, magma....Because many more people are manipulating �XML �every day than connecting to Cassandra ?�So now XML is fixed, not it fails due to a problem in the Mock package...We can not delay a release to fix all foreign packages. This makes no sense.Norbert