Hi Laurent: I suffer that too. Actually, much more than everybody as I build the dev images. Stef: condeseChanges is automatically called after installing ConfiguratioOfPharo as the default grouo loads the DEV group which includes all the dev tools an ImageForDevelopers. This, does some cleanUps included condeseChanges. In the past, there was no poblem to do it even if it was not strictly needed. Now, it's different. So, my proposal is: remove the condenseChanges from the cleanUps of ImageForDevelopers, and I add it to my post bash scripts when building the dev image. Do you agree? Cheers Mariano 2010/5/17 laurent laffont <laurent.laffont@gmail.com>
It has just finished :)
Laurent
On Mon, May 17, 2010 at 10:40 PM, laurent laffont < laurent.laffont@gmail.com> wrote:
I'm starting to wonder if this condensing will ever finish !
Laurent
On Mon, May 17, 2010 at 10:37 PM, Stéphane Ducasse < stephane.ducasse@inria.fr> wrote:
don't bother :)
It is taking long but fully working. We will condense it for may be beta or rc depending on the size.
Stef
Hi,
I've just started playing with ConfigurationOfPharo 1.1 and I'm currently experiencing the looooong "condensing changes file". I have currently troubles trying to follow all the traffic of this mailing-list :) but is there some work to make it far less longer ? or optional ?
Laurent Laffont
http://pharocasts.blogspot.com/ http://magaloma.blogspot.com/ _______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project