January 2010 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] [BetaTesting] [ANN] Pharo1.0-10505-rc1dev10.01.1

by Schwab,Wilhelm K

Mariano, I'm aware of ScriptLoader because it is in the image, and presumably I was either told to use it or turned it up by browsing, perhaps for something that would load FFI. If the image is missing critical pieces (FFI, Seaside, etc.), do not be surprised when people resort to search engines and browsers, and might find broken code or things that you do not want them to use. Bill ________________________________ From: pharo-project-bounces(a)lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Mariano Martinez Peck Sent: Saturday, January 09, 2010 7:05 PM To: Pharo-project(a)lists.gforge.inria.fr Subject: Re: [Pharo-project] [BetaTesting] [ANN] Pharo1.0-10505-rc1dev10.01.1 On Sun, Jan 10, 2010 at 12:35 AM, Schwab,Wilhelm K <bschwab(a)anest.ufl.edu<mailto:bschwab@anest.ufl.edu>> wrote: Matthias, That appears to have worked. Let's see, we have Installer, ScriptLoader, ScriptLoader is for internal use. If you use it, you are doing something wrong. You should not even be aware of that. Configuration*, Is the package managment. If you don't want to have to install all of the dependencies of all packages, and you don't want stable versions, don't use it. Gofer, If you don't want to automate your downloads, don't use it. You can use the Monticello Browser if you want. etc., and now Loader =:0 Loader is not even in beta. And it is just a wrap to make Metacello easier. I'm guilty too, because I ended up writing Migrate in self defense. Clearly something is missing in package management or we would not have so many different solutions to strongly overlapping problems. I will have to repeat this because Loader new load: 'Pharo' version: '1.0-rc2.10505'. did not seem to do much - makes me wonder whether I really ran it. If not, then it appears not to be necessary for Seaside to at least load. If this is in fact the correct way to install Seaside (I submit we need direction on that, unless you or Esteban are the authoritative source??), then it needs to get a link on the download page. Therein, we should refer to (Smalltalk at:#Loader) rather than directly to Loader. Please convey my thanks and respect to Esteban - not sure I want to know *how* this works :) Esteban is in holidays for 2 weeks. In summary, in my point of view, we now have to concentrate in use Metacello configurations. How you download your ConfXX is your problem. If you want to use Gofer, use it, if don't, user Monticello Browser. Don't use ScriptLoader. Loader shouldn't be used until we are more stable. Cheers Mariano Thanks!! Bill -----Original Message----- From: pharo-project-bounces(a)lists.gforge.inria.fr<mailto:pharo-project-bounces@lists.gforge.inria.fr> [mailto:pharo-project-bounces@lists.gforge.inria.fr<mailto:pharo-project-bounces@lists.gforge.inria.fr>] On Behalf Of Matthias Berth Sent: Saturday, January 09, 2010 6:09 PM To: Pharo-project(a)lists.gforge.inria.fr<mailto:Pharo-project@lists.gforge.inria.fr> Subject: Re: [Pharo-project] [BetaTesting] [ANN] Pharo1.0-10505-rc1dev10.01.1 Hi Bill, this one works for me with the current pharo core 1.0 rc1, update upto 10505 "execute this:" Gofer new squeaksource: 'Loader'; package: 'Loader'; load. "then this" Loader new load: 'Pharo' version: '1.0-rc2.10505'. "then this" Loader new load: 'Seaside28' version: '2.8.4.2' The "Loader new load: 'Pharo' version: '1.0-rc2.10505'." loads a lot of additional pharo packages. I guess you won't need that just to get seaside working. Ask Esteban Lorenzano for details about hw this works :) Cheers Matthias 2010/1/9 Schwab,Wilhelm K <bschwab(a)anest.ufl.edu<mailto:bschwab@anest.ufl.edu>>: > Two can be tired of this. I could just use the official Seaside > images, but I thought it might be nice to help with testing the > monthly images. I won't get very far with that if Seaside won't load. > > > ________________________________ > From: pharo-project-bounces(a)lists.gforge.inria.fr<mailto:pharo-project-bounces@lists.gforge.inria.fr> > [mailto:pharo-project-bounces@lists.gforge.inria.fr<mailto:pharo-project-bounces@lists.gforge.inria.fr>] On Behalf Of > Mariano Martinez Peck > Sent: Saturday, January 09, 2010 4:38 PM > To: Pharo-project(a)lists.gforge.inria.fr<mailto:Pharo-project@lists.gforge.inria.fr> > Subject: Re: [Pharo-project] [BetaTesting] [ANN] > Pharo1.0-10505-rc1dev10.01.1 > > > > 2010/1/9 Schwab,Wilhelm K <bschwab(a)anest.ufl.edu<mailto:bschwab@anest.ufl.edu>> >> >> Mariano, >> >> The reason I objected (and continue to do so) to clobbering the web >> image is that complete chaos of how to install things comes into >> play. Assuming that I know what YOU said on the subject is a stretch >> to say the least: try a search engine on the subject. >> > > I am a bit tired of this. I will answer for the last time and I hope > you > understand: Do you want seaside ? > > 1) Volunteer yourself to build Web images. It is easy to ask, but what > about doing? > > 2) Take the Web Image before, analize how seaside was installed and do > it by yourself. I cannot take it more than half an hour. > > 3) Use official seaside image > > 4) Report what doesn't work with the ConfigurationOfSeaside in > Metacello mailing list so that everybody can collaborate and fix it. > If you see that mailing list, I did exactly that. Just saying "doesn't work" does not help. > > Cheers > > Mariano > >> >> BTW, it does not work. There is very little I can do until Seaside loads. >> >> Bill >> >> ________________________________ >> From: pharo-project-bounces(a)lists.gforge.inria.fr<mailto:pharo-project-bounces@lists.gforge.inria.fr> >> [mailto:pharo-project-bounces@lists.gforge.inria.fr<mailto:pharo-project-bounces@lists.gforge.inria.fr>] On Behalf Of >> Mariano Martinez Peck >> Sent: Saturday, January 09, 2010 4:08 PM >> To: Pharo-project(a)lists.gforge.inria.fr<mailto:Pharo-project@lists.gforge.inria.fr> >> Subject: Re: [Pharo-project] [BetaTesting] [ANN] >> Pharo1.0-10505-rc1dev10.01.1 >> >> >> >> 2010/1/9 Schwab,Wilhelm K <bschwab(a)anest.ufl.edu<mailto:bschwab@anest.ufl.edu>> >>> >>> Gofer seaside28 load >>> >> >> I didn't say that. I said: >> >> Gofer new >> squeaksource: 'MetacelloRepository'; >> package: 'ConfigurationOfSeaside28'; >> load. >> >> (Smalltalk at: #ConfigurationOfSeaside28) load >> >> And I also said I was not sure of this is working. >> >> Cheers >> >> Mariano >> >>> >>> does not work. What is the correct way to install Seaside - I can't >>> do much w/o it. >>> >>> ________________________________ >>> From: pharo-project-bounces(a)lists.gforge.inria.fr<mailto:pharo-project-bounces@lists.gforge.inria.fr> >>> [mailto:pharo-project-bounces@lists.gforge.inria.fr<mailto:pharo-project-bounces@lists.gforge.inria.fr>] On Behalf Of >>> Mariano Martinez Peck >>> Sent: Saturday, January 09, 2010 3:01 PM >>> To: Pharo-project(a)lists.gforge.inria.fr<mailto:Pharo-project@lists.gforge.inria.fr> >>> Subject: Re: [Pharo-project] [BetaTesting] [ANN] >>> Pharo1.0-10505-rc1dev10.01.1 >>> >>> >>> >>> 2010/1/9 Miguel Enrique CobÃ¡ Martinez <miguel.coba(a)gmail.com<mailto:miguel.coba@gmail.com>> >>>> >>>> Hi Mariano, >>>> >>>> good job. Some feedback. >>>> >>>> The installScript has unused variables and your proxy settings exposed. >>>> Maybe this should be deleted from the final build. >>>> >>> >>> hahahahah I knew I was going to forget about that :( Thanks. Some >>> bash guru that help me to automatize this? I would like something >>> that automatically removes that from the file if it is found. >>> Can you help me Miguel ? >>> >>>> >>>> Shouldn't be this a RC 2? because there is a new build process and >>>> has nothing to do with the RC1? >>>> >>> >>> I thought about putting it RC2, actually, I was going to do that. >>> But as the PharoCore was named rc1, I din't want to name it rc2 >>> because maybe it was confusing. >>> I am not sure, thus. What do you think ? >>> >>>> >>>> Also, the changes files, shouldn't be compressed for each RC and >>>> for the final release? >>> >>> Excellent point. Do you rather to Smalltalk >> condenseChanges ? It >>> can be perfectly added. Right now, we are doing all this: >>> >>> >>> MCFileBasedRepository flushAllCaches. >>> MCDefinition clearInstances. >>> Smalltalk removeEmptyMessageCategories. >>> Utilities cleanseOtherworldlySteppers. >>> Undeclared removeUnreferencedKeys. >>> Categorizer sortAllCategories. >>> Symbol compactSymbolTable. >>> Smalltalk at: #ReleaseBuilderDeveloper ifPresent: [:builder | >>> builder new fixObsoleteReferences]. >>> RequiredSelectors initialize. >>> ProvidedSelectors initialize. >>> LocalSends initialize. >>> Smalltalk organization removeEmptyCategories. >>> SystemBrowser removeObsolete. >>> TheWorldMenu removeObsolete. >>> AppRegistry removeObsolete. >>> Set rehashAllSets. >>> Smalltalk cleanOutUndeclared. >>> Smalltalk garbageCollect. >>> >>> >>> Do you think something else should be addded? Maybe we can reuse >>> ScriptLoader cleanings ? >>> >>> >>>> >>>> Also, the packages.txt file talks about PharoCore1.0 (#10505). Has >>>> someone thought about the name shown in System->About: >>>> >>>> PharoCore1.0rc1 >>>> Latest update: #10505 >>>> >>>> Because this is not a PharoCore image. Shouldn't this read >>>> something like >>>> >>>> Pharo 1.0 Dev image. >>>> Based on PharoCore1.0rc1 >>>> Latest update: #10505 >>>> >>> >>> Yes, that's true. I agree. At least it was not "my falt" as it was >>> already like that. But I am agree we should change that. However, I >>> don't know how to do it. >>> Maybe something related to SystemVersion? Any help ? >>> >>> >>>> >>>> What about the disabling of software updates in the Pharo dev/web >>>> images? Will this be implemented or a careful update stream will be >>>> made in order to not break a dev image with overrides (real >>>> difficult I think). >>>> >>> >>> Maybe. But in addition, sometimes there are bugs that updating just >>> fix them. I am not sure if I want to disable. I rather warn people about it. >>> Do you know if we break some overrrides doing an update? >>> >>>> >>>> Maybe all this setup can be put in a post-script in the >>>> ConfigurationOfPharo class. >>> >>> It is. We have pre and post do its. So, no problem :) >>> >>>> >>>> That's all for now. I'm going to use this image to work the >>>> following days. >>>> >>>> >>>> Cheers and keep the good work. >>>> >>> >>> Thanks Miguel for the excellent feedback. Let's hope to build better >>> images! >>> >>> Mariano >>> >>> >>>> >>>> -- >>>> Miguel CobÃ¡ >>>> http://miguel.leugim.com.mx >>>> >>>> >>>> _______________________________________________ >>>> Pharo-project mailing list >>>> Pharo-project(a)lists.gforge.inria.fr<mailto:Pharo-project@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<mailto:Pharo-project@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<mailto:Pharo-project@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<mailto:Pharo-project@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<mailto:Pharo-project@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<mailto:Pharo-project@lists.gforge.inria.fr> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Jan. 10, 2010

Re: [Pharo-project] [BetaTesting] [ANN] Pharo1.0-10505-rc1dev10.01.1

by Mariano Martinez Peck

2010/1/9 Miguel Enrique CobÃ¡ Martinez <miguel.coba(a)gmail.com> > El sÃ¡b, 09-01-2010 a las 21:00 +0100, Mariano Martinez Peck escribiÃ³: > > > > > > 2010/1/9 Miguel Enrique CobÃ¡ Martinez <miguel.coba(a)gmail.com> > > Hi Mariano, > > > > good job. Some feedback. > > > > The installScript has unused variables and your proxy settings > > exposed. > > Maybe this should be deleted from the final build. > > > > > > hahahahah I knew I was going to forget about that :( > > Thanks. Some bash guru that help me to automatize this? I would like > > something that automatically removes that from the file if it is > > found. > > Can you help me Miguel ? > > Maybe you can use two scripts, one for configuring the proxy and other > for the gofer/metacello configuration. Then before zipping the files, > delete the proxy settings one. Also, don't the settings remain > configured in the image on the snapshot:andQuit message. If so, a > post-script to clear the parameter is needed too. > > Thanks Miguel. I really appreciate this kind of feedback. It is fixed now. > > > > > > Shouldn't be this a RC 2? because there is a new build process > > and has > > nothing to do with the RC1? > > > > > > I thought about putting it RC2, actually, I was going to do that. But > > as the PharoCore was named rc1, I din't want to name it rc2 because > > maybe it was confusing. > > I am not sure, thus. What do you think ? > > I think that is good to have a RC2. Also this shows progress to the > public. > > Ok, next release will be rc2. > > > > Also, the changes files, shouldn't be compressed for each RC > > and for the > > final release? > > > > Excellent point. Do you rather to Smalltalk >> condenseChanges ? It > > can be perfectly added. Right now, we are doing all this: > > I don't know the exact message to condense changes, but if it is that > then yes, should be added near the end of the other instructions. > > > > > > MCFileBasedRepository flushAllCaches. > > MCDefinition clearInstances. > > Smalltalk removeEmptyMessageCategories. > > Utilities cleanseOtherworldlySteppers. > > Undeclared removeUnreferencedKeys. > > Categorizer sortAllCategories. > > Symbol compactSymbolTable. > > Smalltalk at: #ReleaseBuilderDeveloper ifPresent: [:builder | > > builder new fixObsoleteReferences]. > > RequiredSelectors initialize. > > ProvidedSelectors initialize. > > LocalSends initialize. > > Smalltalk organization removeEmptyCategories. > > SystemBrowser removeObsolete. > > TheWorldMenu removeObsolete. > > AppRegistry removeObsolete. > > Set rehashAllSets. > > Smalltalk cleanOutUndeclared. > > Smalltalk garbageCollect. > > > > Respect to this list, and maybe this should be a ticket. Shouldn't be > better to have an established message to cleanup the image on release. > Something like the cleanUpForImageRelease but generalized and then, the > classes that need to do something like this, they implement that > message. > > So on release a new image version you only call something like > > Smalltalk cleanUpForImageRelease. > > It is already in ScriptLoader >> cleanUpForRelease I will try to look at the differences with ImageForDevelopers >> cleanUpMemory and see what can I do. > and inside it search all the classes that implements the message and > call them. So, your post-script becomes a single line and each package > is responsible of putting inside its own cleanUpForImageRelease whatever > needed to initialize itself. > But well, just an idea for subsequent releases. > > > > > Do you think something else should be addded? Maybe we can reuse > > ScriptLoader cleanings ? > > Yes, and also the GarbageCollector parameters that John McIntosh is > preparing. This must be part of Pharo 1.0 without doubts. > > I am now aware of this. > > > > > > > > > > Also, the packages.txt file talks about PharoCore1.0 (#10505). > > Has > > someone thought about the name shown in System->About: > > > > PharoCore1.0rc1 > > Latest update: #10505 > > > > Because this is not a PharoCore image. Shouldn't this read > > something > > like > > > > Pharo 1.0 Dev image. > > Based on PharoCore1.0rc1 > > Latest update: #10505 > > > > > > Yes, that's true. I agree. At least it was not "my falt" as it was > > already like that. But I am agree we should change that. However, I > > don't know how to do it. > > Maybe something related to SystemVersion? Any help ? > > > > > > What about the disabling of software updates in the Pharo > > dev/web > > images? Will this be implemented or a careful update stream > > will be made > > in order to not break a dev image with overrides (real > > difficult I > > think). > > > > > > Maybe. But in addition, sometimes there are bugs that updating just > > fix them. I am not sure if I want to disable. I rather warn people > > about it. > > Yes, both options have pros and cons. > > Pros > - Can fix bugs after release > - Can aply improvements to the image after release. > > Cons > - Can mess the image of someone by overwriting some overridden method. > - Can accidentally update more than intended in someone's image > > Should we vote? > > yes, send a separate email with this to hear opinions. > > Do you know if we break some overrrides doing an update? > > > > Maybe all this setup can be put in a post-script in the > > ConfigurationOfPharo class. > > > > It is. We have pre and post do its. So, no problem :) > > > > > > That's all for now. I'm going to use this image to work the > > following > > days. > > > > Cheers and keep the good work. > > > Thanks Miguel for the excellent feedback. Let's hope to build better > > images! > > > > Mariano > > > Cheers > > -- > Miguel CobÃ¡ > http://miguel.leugim.com.mx > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Jan. 10, 2010

Re: [Pharo-project] [BetaTesting] [ANN] Pharo1.0-10505-rc1dev10.01.1

by Mariano Martinez Peck

On Sun, Jan 10, 2010 at 12:35 AM, Schwab,Wilhelm K <bschwab(a)anest.ufl.edu>wrote: > Matthias, > > That appears to have worked. Let's see, we have Installer, ScriptLoader, ScriptLoader is for internal use. If you use it, you are doing something wrong. You should not even be aware of that. > Configuration*, Is the package managment. If you don't want to have to install all of the dependencies of all packages, and you don't want stable versions, don't use it. > Gofer, If you don't want to automate your downloads, don't use it. You can use the Monticello Browser if you want. > etc., and now Loader =:0 Loader is not even in beta. And it is just a wrap to make Metacello easier. > I'm guilty too, because I ended up writing Migrate in self defense. > Clearly something is missing in package management or we would not have so > many different solutions to strongly overlapping problems. > > I will have to repeat this because > > Loader new load: 'Pharo' version: '1.0-rc2.10505'. > > did not seem to do much - makes me wonder whether I really ran it. If not, > then it appears not to be necessary for Seaside to at least load. > > If this is in fact the correct way to install Seaside (I submit we need > direction on that, unless you or Esteban are the authoritative source??), > then it needs to get a link on the download page. Therein, we should refer > to (Smalltalk at:#Loader) rather than directly to Loader. > > Please convey my thanks and respect to Esteban - not sure I want to know > *how* this works :) > Esteban is in holidays for 2 weeks. In summary, in my point of view, we now have to concentrate in use Metacello configurations. How you download your ConfXX is your problem. If you want to use Gofer, use it, if don't, user Monticello Browser. Don't use ScriptLoader. Loader shouldn't be used until we are more stable. Cheers Mariano > Thanks!! > > Bill > > > > -----Original Message----- > From: pharo-project-bounces(a)lists.gforge.inria.fr [mailto: > pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of Matthias Berth > Sent: Saturday, January 09, 2010 6:09 PM > To: Pharo-project(a)lists.gforge.inria.fr > Subject: Re: [Pharo-project] [BetaTesting] [ANN] > Pharo1.0-10505-rc1dev10.01.1 > > Hi Bill, > > this one works for me with the current pharo core 1.0 rc1, update upto > 10505 > > "execute this:" > Gofer new > squeaksource: 'Loader'; > package: 'Loader'; > load. > "then this" > Loader new load: 'Pharo' version: '1.0-rc2.10505'. > "then this" > Loader new > load: 'Seaside28' version: '2.8.4.2' > > The "Loader new load: 'Pharo' version: '1.0-rc2.10505'." loads a lot of > additional pharo packages. I guess you won't need that just to get seaside > working. > > Ask Esteban Lorenzano for details about hw this works :) > > Cheers > > Matthias > > 2010/1/9 Schwab,Wilhelm K <bschwab(a)anest.ufl.edu>: > > Two can be tired of this. I could just use the official Seaside > > images, but I thought it might be nice to help with testing the > > monthly images. I won't get very far with that if Seaside won't load. > > > > > > ________________________________ > > From: pharo-project-bounces(a)lists.gforge.inria.fr > > [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of > > Mariano Martinez Peck > > Sent: Saturday, January 09, 2010 4:38 PM > > To: Pharo-project(a)lists.gforge.inria.fr > > Subject: Re: [Pharo-project] [BetaTesting] [ANN] > > Pharo1.0-10505-rc1dev10.01.1 > > > > > > > > 2010/1/9 Schwab,Wilhelm K <bschwab(a)anest.ufl.edu> > >> > >> Mariano, > >> > >> The reason I objected (and continue to do so) to clobbering the web > >> image is that complete chaos of how to install things comes into > >> play. Assuming that I know what YOU said on the subject is a stretch > >> to say the least: try a search engine on the subject. > >> > > > > I am a bit tired of this. I will answer for the last time and I hope > > you > > understand: Do you want seaside ? > > > > 1) Volunteer yourself to build Web images. It is easy to ask, but what > > about doing? > > > > 2) Take the Web Image before, analize how seaside was installed and do > > it by yourself. I cannot take it more than half an hour. > > > > 3) Use official seaside image > > > > 4) Report what doesn't work with the ConfigurationOfSeaside in > > Metacello mailing list so that everybody can collaborate and fix it. > > If you see that mailing list, I did exactly that. Just saying "doesn't > work" does not help. > > > > Cheers > > > > Mariano > > > >> > >> BTW, it does not work. There is very little I can do until Seaside > loads. > >> > >> Bill > >> > >> ________________________________ > >> From: pharo-project-bounces(a)lists.gforge.inria.fr > >> [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of > >> Mariano Martinez Peck > >> Sent: Saturday, January 09, 2010 4:08 PM > >> To: Pharo-project(a)lists.gforge.inria.fr > >> Subject: Re: [Pharo-project] [BetaTesting] [ANN] > >> Pharo1.0-10505-rc1dev10.01.1 > >> > >> > >> > >> 2010/1/9 Schwab,Wilhelm K <bschwab(a)anest.ufl.edu> > >>> > >>> Gofer seaside28 load > >>> > >> > >> I didn't say that. I said: > >> > >> Gofer new > >> squeaksource: 'MetacelloRepository'; > >> package: 'ConfigurationOfSeaside28'; > >> load. > >> > >> (Smalltalk at: #ConfigurationOfSeaside28) load > >> > >> And I also said I was not sure of this is working. > >> > >> Cheers > >> > >> Mariano > >> > >>> > >>> does not work. What is the correct way to install Seaside - I can't > >>> do much w/o it. > >>> > >>> ________________________________ > >>> From: pharo-project-bounces(a)lists.gforge.inria.fr > >>> [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of > >>> Mariano Martinez Peck > >>> Sent: Saturday, January 09, 2010 3:01 PM > >>> To: Pharo-project(a)lists.gforge.inria.fr > >>> Subject: Re: [Pharo-project] [BetaTesting] [ANN] > >>> Pharo1.0-10505-rc1dev10.01.1 > >>> > >>> > >>> > >>> 2010/1/9 Miguel Enrique CobÃ¡ Martinez <miguel.coba(a)gmail.com> > >>>> > >>>> Hi Mariano, > >>>> > >>>> good job. Some feedback. > >>>> > >>>> The installScript has unused variables and your proxy settings > exposed. > >>>> Maybe this should be deleted from the final build. > >>>> > >>> > >>> hahahahah I knew I was going to forget about that :( Thanks. Some > >>> bash guru that help me to automatize this? I would like something > >>> that automatically removes that from the file if it is found. > >>> Can you help me Miguel ? > >>> > >>>> > >>>> Shouldn't be this a RC 2? because there is a new build process and > >>>> has nothing to do with the RC1? > >>>> > >>> > >>> I thought about putting it RC2, actually, I was going to do that. > >>> But as the PharoCore was named rc1, I din't want to name it rc2 > >>> because maybe it was confusing. > >>> I am not sure, thus. What do you think ? > >>> > >>>> > >>>> Also, the changes files, shouldn't be compressed for each RC and > >>>> for the final release? > >>> > >>> Excellent point. Do you rather to Smalltalk >> condenseChanges ? It > >>> can be perfectly added. Right now, we are doing all this: > >>> > >>> > >>> MCFileBasedRepository flushAllCaches. > >>> MCDefinition clearInstances. > >>> Smalltalk removeEmptyMessageCategories. > >>> Utilities cleanseOtherworldlySteppers. > >>> Undeclared removeUnreferencedKeys. > >>> Categorizer sortAllCategories. > >>> Symbol compactSymbolTable. > >>> Smalltalk at: #ReleaseBuilderDeveloper ifPresent: [:builder | > >>> builder new fixObsoleteReferences]. > >>> RequiredSelectors initialize. > >>> ProvidedSelectors initialize. > >>> LocalSends initialize. > >>> Smalltalk organization removeEmptyCategories. > >>> SystemBrowser removeObsolete. > >>> TheWorldMenu removeObsolete. > >>> AppRegistry removeObsolete. > >>> Set rehashAllSets. > >>> Smalltalk cleanOutUndeclared. > >>> Smalltalk garbageCollect. > >>> > >>> > >>> Do you think something else should be addded? Maybe we can reuse > >>> ScriptLoader cleanings ? > >>> > >>> > >>>> > >>>> Also, the packages.txt file talks about PharoCore1.0 (#10505). Has > >>>> someone thought about the name shown in System->About: > >>>> > >>>> PharoCore1.0rc1 > >>>> Latest update: #10505 > >>>> > >>>> Because this is not a PharoCore image. Shouldn't this read > >>>> something like > >>>> > >>>> Pharo 1.0 Dev image. > >>>> Based on PharoCore1.0rc1 > >>>> Latest update: #10505 > >>>> > >>> > >>> Yes, that's true. I agree. At least it was not "my falt" as it was > >>> already like that. But I am agree we should change that. However, I > >>> don't know how to do it. > >>> Maybe something related to SystemVersion? Any help ? > >>> > >>> > >>>> > >>>> What about the disabling of software updates in the Pharo dev/web > >>>> images? Will this be implemented or a careful update stream will be > >>>> made in order to not break a dev image with overrides (real > >>>> difficult I think). > >>>> > >>> > >>> Maybe. But in addition, sometimes there are bugs that updating just > >>> fix them. I am not sure if I want to disable. I rather warn people > about it. > >>> Do you know if we break some overrrides doing an update? > >>> > >>>> > >>>> Maybe all this setup can be put in a post-script in the > >>>> ConfigurationOfPharo class. > >>> > >>> It is. We have pre and post do its. So, no problem :) > >>> > >>>> > >>>> That's all for now. I'm going to use this image to work the > >>>> following days. > >>>> > >>>> > >>>> Cheers and keep the good work. > >>>> > >>> > >>> Thanks Miguel for the excellent feedback. Let's hope to build better > >>> images! > >>> > >>> Mariano > >>> > >>> > >>>> > >>>> -- > >>>> Miguel CobÃ¡ > >>>> http://miguel.leugim.com.mx > >>>> > >>>> > >>>> _______________________________________________ > >>>> 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 > > > > _______________________________________________ > 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 >

Jan. 10, 2010

Re: [Pharo-project] [BetaTesting] [ANN] Pharo1.0-10505-rc1dev10.01.1

by Schwab,Wilhelm K

Mariano, Whether it makes sense or not, try it yourself. Either Loader is more than you think it is, or it does something that is critical to allowing Metacello to succeed. Bill ________________________________ From: pharo-project-bounces(a)lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Mariano Martinez Peck Sent: Saturday, January 09, 2010 6:37 PM To: Pharo-project(a)lists.gforge.inria.fr Subject: Re: [Pharo-project] [BetaTesting] [ANN] Pharo1.0-10505-rc1dev10.01.1 2010/1/10 Miguel Enrique CobÃ¡ Martinez <miguel.coba(a)gmail.com<mailto:miguel.coba@gmail.com>> El dom, 10-01-2010 a las 00:08 +0100, Matthias Berth escribiÃ³: > Hi Bill, > > this one works for me with the current pharo core 1.0 rc1, update upto 10505 > > "execute this:" > Gofer new > squeaksource: 'Loader'; > package: 'Loader'; > load. > "then this" > Loader new load: 'Pharo' version: '1.0-rc2.10505'. > "then this" > Loader new > load: 'Seaside28' version: '2.8.4.2' > > The "Loader new load: 'Pharo' version: '1.0-rc2.10505'." loads a lot > of additional pharo packages. I guess you won't need that just to get > seaside working. > But isn't the loader alpha yet? Maybe even before. Hoever, it does not make sense. Loader is just a simplifier API to metacello. If Loader works with Seaside2.8, ConfigurationOfSeaside28 MUST work too. I mean, I am really expecting for Esteban to release it because is more concise to write commands, but the issue here is the testing of the 1.0 release of pharo with the current available/stable tools, that is, monticello, gofer and metacello. Yes, please. Let's try to use this tools first. When we are stable enough we start with another ones. Cheers Mariano Cheers -- Miguel CobÃ¡ http://miguel.leugim.com.mx _______________________________________________ Pharo-project mailing list Pharo-project(a)lists.gforge.inria.fr<mailto:Pharo-project@lists.gforge.inria.fr> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Jan. 10, 2010

Re: [Pharo-project] [BetaTesting] [ANN] Pharo1.0-10505-rc1dev10.01.1

by Schwab,Wilhelm K

Miguel, My concern is over testing of the RC images. Whether Loader is alpha or not seems a little less important than providing what people will need in order to test. As a friend of mine would say, "don't make it hard on people to help you." I will gladly download a web image, run something in production, or run an alpha installer. The important thing is to have a clear message and a working solution to the problem. Bill -----Original Message----- From: pharo-project-bounces(a)lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Miguel Enrique CobÃ¡ Martinez Sent: Saturday, January 09, 2010 6:21 PM To: Pharo-project(a)lists.gforge.inria.fr Subject: Re: [Pharo-project] [BetaTesting] [ANN] Pharo1.0-10505-rc1dev10.01.1 El dom, 10-01-2010 a las 00:08 +0100, Matthias Berth escribiÃ³: > Hi Bill, > > this one works for me with the current pharo core 1.0 rc1, update upto > 10505 > > "execute this:" > Gofer new > squeaksource: 'Loader'; > package: 'Loader'; > load. > "then this" > Loader new load: 'Pharo' version: '1.0-rc2.10505'. > "then this" > Loader new > load: 'Seaside28' version: '2.8.4.2' > > The "Loader new load: 'Pharo' version: '1.0-rc2.10505'." loads a lot > of additional pharo packages. I guess you won't need that just to get > seaside working. > But isn't the loader alpha yet? I mean, I am really expecting for Esteban to release it because is more concise to write commands, but the issue here is the testing of the 1.0 release of pharo with the current available/stable tools, that is, monticello, gofer and metacello. Cheers -- Miguel CobÃ¡ http://miguel.leugim.com.mx _______________________________________________ Pharo-project mailing list Pharo-project(a)lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Jan. 9, 2010

Re: [Pharo-project] [BetaTesting] [ANN] Pharo1.0-10505-rc1dev10.01.1

by Mariano Martinez Peck

2010/1/10 Miguel Enrique CobÃ¡ Martinez <miguel.coba(a)gmail.com> > El dom, 10-01-2010 a las 00:08 +0100, Matthias Berth escribiÃ³: > > Hi Bill, > > > > this one works for me with the current pharo core 1.0 rc1, update upto > 10505 > > > > "execute this:" > > Gofer new > > squeaksource: 'Loader'; > > package: 'Loader'; > > load. > > "then this" > > Loader new load: 'Pharo' version: '1.0-rc2.10505'. > > "then this" > > Loader new > > load: 'Seaside28' version: '2.8.4.2' > > > > The "Loader new load: 'Pharo' version: '1.0-rc2.10505'." loads a lot > > of additional pharo packages. I guess you won't need that just to get > > seaside working. > > > > But isn't the loader alpha yet? > Maybe even before. Hoever, it does not make sense. Loader is just a simplifier API to metacello. If Loader works with Seaside2.8, ConfigurationOfSeaside28 MUST work too. > > I mean, I am really expecting for Esteban to release it because is more > concise to write commands, but the issue here is the testing of the 1.0 > release of pharo with the current available/stable tools, that is, > monticello, gofer and metacello. > > Yes, please. Let's try to use this tools first. When we are stable enough we start with another ones. Cheers Mariano Cheers > > -- > Miguel CobÃ¡ > http://miguel.leugim.com.mx > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Jan. 9, 2010

Re: [Pharo-project] [BetaTesting] [ANN] Pharo1.0-10505-rc1dev10.01.1

by Schwab,Wilhelm K

Matthias, That appears to have worked. Let's see, we have Installer, ScriptLoader, Configuration*, Gofer, etc., and now Loader =:0 I'm guilty too, because I ended up writing Migrate in self defense. Clearly something is missing in package management or we would not have so many different solutions to strongly overlapping problems. I will have to repeat this because Loader new load: 'Pharo' version: '1.0-rc2.10505'. did not seem to do much - makes me wonder whether I really ran it. If not, then it appears not to be necessary for Seaside to at least load. If this is in fact the correct way to install Seaside (I submit we need direction on that, unless you or Esteban are the authoritative source??), then it needs to get a link on the download page. Therein, we should refer to (Smalltalk at:#Loader) rather than directly to Loader. Please convey my thanks and respect to Esteban - not sure I want to know *how* this works :) Thanks!! Bill -----Original Message----- From: pharo-project-bounces(a)lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Matthias Berth Sent: Saturday, January 09, 2010 6:09 PM To: Pharo-project(a)lists.gforge.inria.fr Subject: Re: [Pharo-project] [BetaTesting] [ANN] Pharo1.0-10505-rc1dev10.01.1 Hi Bill, this one works for me with the current pharo core 1.0 rc1, update upto 10505 "execute this:" Gofer new squeaksource: 'Loader'; package: 'Loader'; load. "then this" Loader new load: 'Pharo' version: '1.0-rc2.10505'. "then this" Loader new load: 'Seaside28' version: '2.8.4.2' The "Loader new load: 'Pharo' version: '1.0-rc2.10505'." loads a lot of additional pharo packages. I guess you won't need that just to get seaside working. Ask Esteban Lorenzano for details about hw this works :) Cheers Matthias 2010/1/9 Schwab,Wilhelm K <bschwab(a)anest.ufl.edu>: > Two can be tired of this.Â I could just use the official Seaside > images, but I thought it might be nice to help with testing the > monthly images.Â I won't get very far with that if Seaside won't load. > > > ________________________________ > From: pharo-project-bounces(a)lists.gforge.inria.fr > [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of > Mariano Martinez Peck > Sent: Saturday, January 09, 2010 4:38 PM > To: Pharo-project(a)lists.gforge.inria.fr > Subject: Re: [Pharo-project] [BetaTesting] [ANN] > Pharo1.0-10505-rc1dev10.01.1 > > > > 2010/1/9 Schwab,Wilhelm K <bschwab(a)anest.ufl.edu> >> >> Mariano, >> >> The reason I objected (and continue to do so) to clobbering the web >> image is that complete chaos of how to install things comes into >> play.Â Assuming that I know what YOU said on the subject is a stretch >> to say the least: try a search engine on the subject. >> > > I am a bit tired of this. I will answer for the last time and I hope > you > understand: Do you want seaside ? > > 1) Volunteer yourself to build Web images. It is easy to ask, but what > about doing? > > 2) Take the Web Image before, analize how seaside was installed and do > it by yourself. I cannot take it more than half an hour. > > 3) Use official seaside image > > 4) Report what doesn't work with the ConfigurationOfSeaside in > Metacello mailing list so that everybody can collaborate and fix it. > If you see that mailing list, I did exactly that. Just saying "doesn't work"Â does not help. > > Cheers > > Mariano > >> >> BTW, it does not work.Â There is very little I can do until Seaside loads. >> >> Bill >> >> ________________________________ >> From: pharo-project-bounces(a)lists.gforge.inria.fr >> [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of >> Mariano Martinez Peck >> Sent: Saturday, January 09, 2010 4:08 PM >> To: Pharo-project(a)lists.gforge.inria.fr >> Subject: Re: [Pharo-project] [BetaTesting] [ANN] >> Pharo1.0-10505-rc1dev10.01.1 >> >> >> >> 2010/1/9 Schwab,Wilhelm K <bschwab(a)anest.ufl.edu> >>> >>> Gofer seaside28 load >>> >> >> I didn't say that. I said: >> >> Gofer new >> Â Â Â squeaksource: 'MetacelloRepository'; >> Â Â Â package: 'ConfigurationOfSeaside28'; >> Â Â Â load. >> >> (Smalltalk at: #ConfigurationOfSeaside28) load >> >> And I also said I was not sure of this is working. >> >> Cheers >> >> Mariano >> >>> >>> does not work.Â What is the correct way to install Seaside - I can't >>> do much w/o it. >>> >>> ________________________________ >>> From: pharo-project-bounces(a)lists.gforge.inria.fr >>> [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of >>> Mariano Martinez Peck >>> Sent: Saturday, January 09, 2010 3:01 PM >>> To: Pharo-project(a)lists.gforge.inria.fr >>> Subject: Re: [Pharo-project] [BetaTesting] [ANN] >>> Pharo1.0-10505-rc1dev10.01.1 >>> >>> >>> >>> 2010/1/9 Miguel Enrique CobÃ¡ Martinez <miguel.coba(a)gmail.com> >>>> >>>> Hi Mariano, >>>> >>>> good job. Some feedback. >>>> >>>> The installScript has unused variables and your proxy settings exposed. >>>> Maybe this should be deleted from the final build. >>>> >>> >>> hahahahah I knew I was going to forget about that :( Thanks. Some >>> bash guru that help me to automatize this? I would like something >>> that automatically removes that from the file if it is found. >>> Can you help me Miguel ? >>> >>>> >>>> Shouldn't be this a RC 2? because there is a new build process and >>>> has nothing to do with the RC1? >>>> >>> >>> I thought about putting it RC2, actually, I was going to do that. >>> But as the PharoCore was named rc1, I din't want to name it rc2 >>> because maybe it was confusing. >>> I am not sure, thus. What do you think ? >>> >>>> >>>> Also, the changes files, shouldn't be compressed for each RC and >>>> for the final release? >>> >>> Excellent point. Do you rather to Smalltalk >> condenseChanges ?Â It >>> can be perfectly added. Right now, we are doing all this: >>> >>> >>> Â Â Â MCFileBasedRepository flushAllCaches. >>> Â Â Â MCDefinition clearInstances. >>> Â Â Â Smalltalk removeEmptyMessageCategories. >>> Â Â Â Utilities cleanseOtherworldlySteppers. >>> Â Â Â Undeclared removeUnreferencedKeys. >>> Â Â Â Categorizer sortAllCategories. >>> Â Â Â Symbol compactSymbolTable. >>> Â Â Â Smalltalk at: #ReleaseBuilderDeveloper ifPresent: [:builder | >>> builder new fixObsoleteReferences]. >>> Â Â Â RequiredSelectors initialize. >>> Â Â Â ProvidedSelectors initialize. >>> Â Â Â LocalSends initialize. >>> Â Â Â Smalltalk organization removeEmptyCategories. >>> Â Â Â SystemBrowser removeObsolete. >>> Â Â Â TheWorldMenu removeObsolete. >>> Â Â Â AppRegistry removeObsolete. >>> Â Â Â Set rehashAllSets. >>> Â Â Â Smalltalk cleanOutUndeclared. >>> Â Â Â Smalltalk garbageCollect. >>> >>> >>> Do you think something else should be addded?Â Â Maybe we can reuse >>> ScriptLoader cleanings ? >>> >>> >>>> >>>> Also, the packages.txt file talks about PharoCore1.0 (#10505). Has >>>> someone thought about the name shown in System->About: >>>> >>>> PharoCore1.0rc1 >>>> Latest update: #10505 >>>> >>>> Because this is not a PharoCore image. Shouldn't this read >>>> something like >>>> >>>> Pharo 1.0 Dev image. >>>> Based on PharoCore1.0rc1 >>>> Latest update: #10505 >>>> >>> >>> Yes, that's true. I agree. At least it was not "my falt" as it was >>> already like that. But I am agree we should change that. However, I >>> don't know how to do it. >>> Maybe something related to SystemVersion? Any help ? >>> >>> >>>> >>>> What about the disabling of software updates in the Pharo dev/web >>>> images? Will this be implemented or a careful update stream will be >>>> made in order to not break a dev image with overrides (real >>>> difficult I think). >>>> >>> >>> Maybe. But in addition, sometimes there are bugs that updating just >>> fix them. I am not sure if I want to disable. I rather warn people about it. >>> Do you know if we break some overrrides doing an update? >>> >>>> >>>> Maybe all this setup can be put in a post-script in the >>>> ConfigurationOfPharo class. >>> >>> It is. We have pre and post do its. So, no problem :) >>> >>>> >>>> That's all for now. I'm going to use this image to work the >>>> following days. >>>> >>>> >>>> Cheers and keep the good work. >>>> >>> >>> Thanks Miguel for the excellent feedback. Let's hope to build better >>> images! >>> >>> Mariano >>> >>> >>>> >>>> -- >>>> Miguel CobÃ¡ >>>> http://miguel.leugim.com.mx >>>> >>>> >>>> _______________________________________________ >>>> 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 > _______________________________________________ Pharo-project mailing list Pharo-project(a)lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Jan. 9, 2010

Re: [Pharo-project] Something I don't understand with ImageSegments

by Martin McClure

Lukas Renggli wrote: >>> But I also fail to see why you'd get the class of one of the referenced >>> objects but not Association. >> Yes, I don't understand neither. > > I would expect everything to be in the outPointers. All involved > objects are referenced from the outside through the stack frame that > is still active while creating the segment. No, only the roots are referenced by the stack frame, and that shouldn't change the outcome. Regards, -Martin

Jan. 9, 2010

Re: [Pharo-project] [BetaTesting] [ANN] Pharo1.0-10505-rc1dev10.01.1

by Miguel Enrique CobÃ¡ Martinez

El dom, 10-01-2010 a las 00:08 +0100, Matthias Berth escribiÃ³: > Hi Bill, > > this one works for me with the current pharo core 1.0 rc1, update upto 10505 > > "execute this:" > Gofer new > squeaksource: 'Loader'; > package: 'Loader'; > load. > "then this" > Loader new load: 'Pharo' version: '1.0-rc2.10505'. > "then this" > Loader new > load: 'Seaside28' version: '2.8.4.2' > > The "Loader new load: 'Pharo' version: '1.0-rc2.10505'." loads a lot > of additional pharo packages. I guess you won't need that just to get > seaside working. > But isn't the loader alpha yet? I mean, I am really expecting for Esteban to release it because is more concise to write commands, but the issue here is the testing of the 1.0 release of pharo with the current available/stable tools, that is, monticello, gofer and metacello. Cheers -- Miguel CobÃ¡ http://miguel.leugim.com.mx

Jan. 9, 2010

Re: [Pharo-project] [BetaTesting] [ANN] Pharo1.0-10505-rc1dev10.01.1

by Miguel Enrique CobÃ¡ Martinez

> 6) There is no Web image this time. If you want to install Seaside > 2.8.4 evaluate: > > Gofer new > squeaksource: 'MetacelloRepository'; > package: 'ConfigurationOfSeaside28'; > load. > > (Smalltalk at: #ConfigurationOfSeaside28) load > Tried to install seaside 2.8 with this snippet in the image you published. It gives me an error: MessageNotUnderstood: receiver of "load" is nil when executing: (Smalltalk at: #ConfigurationOfSeaside28) load The method complaining is: MetacelloMCProject(MetacelloProject)>> latestVersion specifically, this part: (self map values select: [:version | (excluded includes: version blessing) not ]) detectMax: [:version | version ] the select gives an empty list and the detectMax returns nil. the excluded temp var has: #(#development #broken #baseline) and the versions of Seaside are blessed as development. Cheers -- Miguel CobÃ¡ http://miguel.leugim.com.mx

Jan. 9, 2010