[Pharo-project] Please publish Slice
because after this is much more difficult for me to integrate For example now I have new event mixed with closure fixes.... This is simple to publish a slice you create it and add the dirty packages as dependent. Stef
OK Stef, sorry I didn't follow the procedure. This is because the annoying fact that running some of the tests result in dirty packages... Nicolas 2009/4/16 Stéphane Ducasse <stephane.ducasse@inria.fr>:
because after this is much more difficult for me to integrate For example now I have new event mixed with closure fixes.... This is simple to publish a slice you create it and add the dirty packages as dependent.
Stef
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
On Apr 16, 2009, at 2:22 PM, Nicolas Cellier wrote:
OK Stef, sorry I didn't follow the procedure. This is because the annoying fact that running some of the tests result in dirty packages...
I see :) Stef
Nicolas
2009/4/16 Stéphane Ducasse <stephane.ducasse@inria.fr>:
because after this is much more difficult for me to integrate For example now I have new event mixed with closure fixes.... This is simple to publish a slice you create it and add the dirty packages as dependent.
Stef
_______________________________________________ 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
On Thu, Apr 16, 2009 at 2:22 PM, Nicolas Cellier <nicolas.cellier.aka.nice@gmail.com> wrote:
OK Stef, sorry I didn't follow the procedure. This is because the annoying fact that running some of the tests result in dirty packages...
Can some Monticello wiz come up with some magic script to run to check all dirty packages for changes, so that packages that don't have changes get reset to clean? Michael
Can some Monticello wiz come up with some magic script to run to check all dirty packages for changes, so that packages that don't have changes get reset to clean?
Seaside 2.9alpha3 has several scripts in the class WADevelopment in the package Seaside-Squeak-Development that do exactly that (and other stuff). If there are many packages involved it takes a long time though. Lukas -- Lukas Renggli http://www.lukas-renggli.ch
participants (4)
-
Lukas Renggli -
Michael Rueger -
Nicolas Cellier -
Stéphane Ducasse