- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Please publish Slice

by Lukas Renggli

> 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

April 16, 2009

Re: [Pharo-project] Please publish Slice

by Michael Rueger

On Thu, Apr 16, 2009 at 2:22 PM, Nicolas Cellier <nicolas.cellier.aka.nice(a)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

April 16, 2009

Re: [Pharo-project] The System Package

by Alexandre Bergel

> I don't have a package registered called 'System', Strange, I do not know what went wrong. Sorry, we should have checked in a fresh image before. > That does not solve the problem of overlapping packages. See > <http://code.google.com/p/seaside/wiki/PackageNaming> for a large > scale packaging scheme that works. Why using - in package names where it is a special character for MC. Why not _ instead? Just wondering. In Moose, we have Moose-All, Moose-OBBrowser, ..., but if one define a package Moose, then we are a kind of screwed. Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

April 16, 2009

Re: [Pharo-project] Please publish Slice

by StÃ©phane Ducasse

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(a)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(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

April 16, 2009

Re: [Pharo-project] Please publish Slice

by Nicolas Cellier

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(a)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(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

April 16, 2009

Re: [Pharo-project] Arg assignement [Fwd: how can we sync]

by Nicolas Cellier

Correct, all the fixes are in PharoInbox. You choose to integrate them or not, they are minor. But I expect you can integrate them all in less than 1 hour. Cheers Nicolas 2009/4/16 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: > ok do I understand correctly that I do not have to have a look > at 'closure usage fixes' :) > > Stef > > On Apr 16, 2009, at 11:51 AM, Nicolas Cellier wrote: > >> No, after a full review of 'Closure Usage Fixes.1.cs', I verified >> this file only fix minor case of blocks writing in outside temps, >> not the case of blocks writing their own arguments. >> >> Nicolas >> >> 2009/4/16 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: >>> Thanks nicolas >>> You are talking about >>> Â Â Â Â http://code.google.com/p/pharo/issues/detail?id=742 >>> >>> Stef >>> >>> On Apr 15, 2009, at 11:10 PM, Nicolas Cellier wrote: >>> >>>> I published very trivials cleanups from Eliots abount Sounds package >>>> in PharoInbox >>>> I will continue reviewing tomorrow. >>>> Bye >>>> >>>> 2009/4/15 Nicolas Cellier <nicolas.cellier.aka.nice(a)gmail.com>: >>>>> Oops, I just miss the attachments :( >>>>> >>>>> 2009/4/15 Nicolas Cellier <nicolas.cellier.aka.nice(a)gmail.com>: >>>>>> >>>>>> Is there a more recent version? >>>>>> >>>>>> Nicolas >>>>>> >>>>> >>>> >>>> _______________________________________________ >>>> Pharo-project mailing list >>>> Pharo-project(a)lists.gforge.inria.fr >>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>>> >>> >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> Pharo-project(a)lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

April 16, 2009

Re: [Pharo-project] New event Sensor

by StÃ©phane Ducasse

ok so I will focus on nicolas fixes first On Apr 16, 2009, at 12:24 PM, Michael Rueger wrote: > On Thu, Apr 16, 2009 at 12:22 PM, StÃ©phane Ducasse > <stephane.ducasse(a)inria.fr> wrote: >> Mike >> >> is it safe to use System-Support (what will happen to inputSensor). > > The packages in the inbox have not been tested yet, but should be > ready later today or tomorrow. > > Michael > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

April 16, 2009

[Pharo-project] Please publish Slice

by StÃ©phane Ducasse

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

April 16, 2009

Re: [Pharo-project] New event Sensor

by Michael Rueger

On Thu, Apr 16, 2009 at 12:22 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Mike > > is it safe to use System-Support (what will happen to inputSensor). The packages in the inbox have not been tested yet, but should be ready later today or tomorrow. Michael

April 16, 2009

[Pharo-project] New event Sensor

by StÃ©phane Ducasse

Mike is it safe to use System-Support (what will happen to inputSensor). Stef

April 16, 2009