- Pharo-dev - lists.pharo.org

Re: [Pharo-project] new to pharo

by StÃ©phane Ducasse

What is important is that we can load the slice. Bcause this is the problem with cs is that you can get packages that you cannot reload. Stef On May 31, 2008, at 11:47 AM, Alexandre Bergel wrote: >>> 1 - Take the latest pharo image, and click on update on the left tab >>> 2 - Open Monticello >>> 3 - Load your .cs file >>> 4 - you should see some package with a * before them in Monticello >>> 5 - Create a package named SLICE-Remove isMorphic message >>> 6 - add to your SLICE package all the packages that have a * >>> before their >>> name as required >>> 7 - Save your SLICE package in PharoInBox > >> I don't understand these instructions: >> >> How do you do step 6? what does adding packages to packages >> mean? > > Right click or (command click if you're on a mac) on a package > listed in a Monticello browser. you will see "add required package". > Add all the packages that are prefixed by a * (resulting from > loading your .cs file). > > >> Slices sounds like MC2. Does Pharo use MC2? > > No. pharo uses MC1. We might switch to MC2 when it is ready, but for > now we stick to something that is reliable. > > I hope this is clearer now. > What Bill meant I guess is to add this information to a wiki. I will > refine what is already written over the time. > > Cheers, > Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

May 31, 2008

Re: [Pharo-project] Re: [Sapphire-devl] sapphire to pharo :)

by StÃ©phane Ducasse

Done. Can you check? I will redo a full upgrade in a clean package cache. Stef On May 31, 2008, at 11:40 AM, Adrian Lienhard wrote: > Hi Stef, > > Today I tried again to load Pharo starting from a fresh 3.9.1 image > but I got the same error when loading "10015-Sap- > FixingInvisibleInTheRest..." (see my mail in this thread from May 16). > > I had a closer look and the problem is that script106 tries to load > Protocols-sd.13.mcz, which does not exist in the repository. > I guess the update worked for you because this file was in your > local cache. Can you copy this package to the repository? > > Adrian

May 31, 2008

Re: [Pharo-project] Re: [Sapphire-devl] sapphire to pharo :)

by StÃ©phane Ducasse

Ok I will Sorry. > Hi Stef, > > Today I tried again to load Pharo starting from a fresh 3.9.1 image > but I got the same error when loading "10015-Sap- > FixingInvisibleInTheRest..." (see my mail in this thread from May 16). > > I had a closer look and the problem is that script106 tries to load > Protocols-sd.13.mcz, which does not exist in the repository. > I guess the update worked for you because this file was in your > local cache. Can you copy this package to the repository? > > Adrian > > > On May 17, 2008, at 08:19 , StÃ©phane Ducasse wrote: > >> Yes this may happen. We are certainly stressing the server. >> Now #hex is really missing in 391. :) >> >> Stef >> >> On May 17, 2008, at 6:40 AM, Victor Rodriguez wrote: >> >>> On Sat, May 17, 2008 at 12:14 AM, Victor Rodriguez >>> <victor.palique(a)gmail.com> wrote: >>> ... >>>> It failed for me in update 10016. I attach the log. >>> >>> It must have been a network error, since started all over again >>> and it >>> is now in update 10020... >>> >>> Victor. >>> >>> _______________________________________________ >>> Sapphire-devl mailing list >>> Sapphire-devl(a)lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/sapphire-devl >>> >> >> >> _______________________________________________ >> Sapphire-devl mailing list >> Sapphire-devl(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/sapphire-devl > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

May 31, 2008

Re: [Pharo-project] Replacing 'ReadStream on smth:' by 'smth readStream'

by StÃ©phane Ducasse

I agree with adrian. I would like to use the stream as a test for Call For Improvement Process. So could you come up with a kind of template Summary: Key points: Some tests to illustrate Actions/Process Stef On May 30, 2008, at 6:17 PM, Adrian Lienhard wrote: > > On May 30, 2008, at 15:37 , Damien Cassou wrote: > >> On Fri, May 30, 2008 at 2:18 PM, Adrian Lienhard <adi(a)netstyle.ch> >> wrote: >>> Have you verified that your change does not inadvertently modify any >>> behavior? Its not likely, but changes like this can introduce >>> subtle bugs. >>> For instance, Matrix overrides readStream. So if there exists any >>> use of >>> "ReadStream on: aMatrix" that is there to bypass the overridden >>> behavior, >>> the code will break. >> >> It should not break anything (if it does, the test will fail and I >> will fix things :-)). In fact, ReadStream only deals with >> SequenceableStreams so it should be ok. Do you agree? > > No I don't agree. Because it is not likely that there is a test for > Matrix that will show a potential bug. I just wanted to point out > that it is important to precisely look at the effect of such > "global" transformations. (E.g. like Edgar tried to replace all #== > with #= IIRC ;) > > With your proposed change, I think it is unlikely you will break > anything, but you cannot say for sure without detailled *manual* > checking. The difficulty is that you theoretically needed to verify > that there is never passed a Matrix instance to "ReadStream on:". > > Also to consider with such changes is that you may break external > code that you don't know of. To sum up, I'm not against such > improvements at all, but they have to be done carefully, i.e., the > argument that tests will show any problem does not hold. > > Cheers, > Adrian > >> -- >> Damien Cassou >> Peter von der AhÃ©: Â«I'm beginning to see why Gilad wished us good >> luckÂ». (http://blogs.sun.com/ahe/entry/override_snafu) >> >> _______________________________________________ >> 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 >

May 31, 2008

Re: [Pharo-project] Replacing 'ReadStream on smth:' by 'smth readStream'

by StÃ©phane Ducasse

>> >> The only potential problem is that you assume tests will catch >> everything. However, I think streams are broken, and I will >> certainly help fix what we break in getting them right. > > I guess the change I'm applying won't cause any problem but I can't be > sure. I won't loose time fixing Streams as I would prefer installing > Nile if everybody agree. Nile seems the way to go. Now could you guys do a summary and proposal with actions. So that we can have one clear summary and situation. stef

May 31, 2008

Re: [Pharo-project] open AtomBouncingMorphs in 3.7 and 3.9 is amazing...

by StÃ©phane Ducasse

> > Stef, > > Let me guess: 3.7 is MUCH faster, right?? Yes but it may be just Morphic. Stef

May 31, 2008

Re: [Pharo-project] [ANN][Pharo-dev] First release

by StÃ©phane Ducasse

Yes!. I would love to have a minimal universe with nothing loaded but so that people can one click load their favorite tools. Stef On May 30, 2008, at 4:12 PM, Damien Cassou wrote: > On Fri, May 30, 2008 at 3:54 PM, Alexandre Bergel > <alexandre(a)bergel.eu> wrote: >> I agree with Bil, it is hard to say whether people will find Pharo- >> dev >> useful. Just give a try :-) > > I was thinking about you guys who are working on Pharo himself. It > seems you all load OB, RB and the other manually. > > > -- > Damien Cassou > Peter von der AhÃ©: Â«I'm beginning to see why Gilad wished us good > luckÂ». (http://blogs.sun.com/ahe/entry/override_snafu) > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

May 31, 2008

[Pharo-project] Fwd: patch for Squeak 3.9.2 / whatever

by StÃ©phane Ducasse

Begin forwarded message: > From: "Philippe Marschall" <philippe.marschall(a)gmail.com> > Date: May 30, 2008 10:52:50 PM CEDT > To: "StÃ©phane Ducasse" <stephane.ducasse(a)inria.fr>, "Adrian > Lienhard" <alienhard(a)netstyle.ch> > Subject: patch for Squeak 3.9.2 / whatever > > http://bugs.squeak.org/view.php?id=6834 >

May 31, 2008

Re: [Pharo-project] [ANN][Pharo-dev] First release

by Damien Cassou

On Fri, May 30, 2008 at 10:26 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > yes we are. > I hope to have a server soon for the universe I think it will be difficult to maintain a universe server (each time you update a package on the squeak universe, you will have to do it again for pharo). -- Damien Cassou Peter von der AhÃ©: Â«I'm beginning to see why Gilad wished us good luckÂ». (http://blogs.sun.com/ahe/entry/override_snafu)

May 31, 2008

[Pharo-project] Fwd: Patch should be applied: Delay class>>timeoutSemaphore:afterMSecs:

by StÃ©phane Ducasse

Begin forwarded message: > From: "Masashi UMEZAWA" <masashi.umezawa(a)gmail.com> > Date: May 31, 2008 4:56:00 AM CEDT > To: "stephane ducasse" <stephane.ducasse(a)free.fr> > Subject: Fwd: Patch should be applied: Delay > class>>timeoutSemaphore:afterMSecs: > > Hi Stef, > > This is just FYI (maybe you do not read v3dot10 list). > > 3.9.1 and Pharo have the same bug also. Networking application would > stop suddenly for this bug... > > ---------- Forwarded message ---------- > From: Masashi UMEZAWA <masashi.umezawa(a)gmail.com> > Date: 2008/5/29 > Subject: Patch should be applied: Delay > class>>timeoutSemaphore:afterMSecs: > To: "Discussion about development of Squeak 3.10" > <v3dot10(a)lists.squeakfoundation.org> > > > Hi all, > > I've downloaded 3.10.1, and found that an important patch on Delay > seems not applied. > > Please see the details on Mantis: > http://bugs.squeak.org/view.php?id=6834 > > Strangely, the patch is not applied on 3.9 series also. I think it is > clearly a bug and it should be fixed. > Socket timeout relies on this method, so the bug is fatal. > > Cheers, > -- > [:masashi | ^umezawa] > > Cheers, > -- > [:masashi | ^umezawa] >

May 31, 2008