Maybe we should ask Dale when time permits to add functionality to Metacello so that can check all the dependencies for a given configuration and make sure (or raise some warning in the validation) that some dependency is refered by a symbolic non numeric version (like #stable, #latestVersion, #bleedingEdge) so that this validation can be run by hudson also and verify that all the configurations are frozen to a given number and no dependent on a symbolic version that can change anytime after release of Pharo when a package get a new (#stable for example) version. Cheers El mié, 23-03-2011 a las 13:26 +0100, Marcus Denker escribió:
On Mar 23, 2011, at 12:52 PM, Torsten Bergmann wrote:
Pharo 1.2 is red again!
DuplicatedVariableError: stylingActive is already defined in Workspace
https://pharo-ic.lille.inria.fr/hudson/view/Pharo/job/Pharo%201.2/195/
We really need to make sure that the config does not load code if we don't explicitly say so.
So what code was changed? Why was it loaded?
-- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.
-- Miguel Cobá http://twitter.com/MiguelCobaMtz http://miguel.leugim.com.mx