Okay I'll dig into this...thanks for confirming. Dale ----- "Alexandre Bergel" <[email protected]> wrote:
| Apparently the bug remains. When I load the last version of | 'ConfigurationOfPharo project' in a fresh and updated Core 1.1, then | | OB-Standard.lr.442 is loaded and initialized. | | So, the problem persists :-) | Thanks Dale for offering your help. | | Cheers, | Alexandre | | | On 29 Apr 2010, at 14:08, Dale Henrichs wrote: | | > Mariano and Alexandre, | > | > Sorry for the late reply ... I've been off-line with a cold for the | | > last several days ... | > | > I have seen the behavior that you describe while working with GLASS | | > 1.0-beta.8 and have fixed the problem in Metacello 1.0-beta.26.1 ... | | > 1.0-beta.26.1 is still in development, but if you want to give it a | | > try, preload 1.0-beta.26.1 and rerun your test ... if the problem | > still persists, let me know and I will dive into it. | > | > Dale | > ----- "Mariano Martinez Peck" <[email protected]> wrote: | > | > | On Wed, Apr 28, 2010 at 11:28 PM, Alexandre Bergel < | > | [email protected]> wrote: | > | | > | > It is a bit more subtle than that. | > | > | > | > If I take a Core 1.1, and doit: ConfigurationOfPharo project | > | lastVersion | > | > load | > | > Then I get a warning coming from OBSearchBrowser class related | to | > | the world | > | > menu registration. | > | > | > | > | > | Yes, I noticed that. | > | | > | | > | > At that moment, OmniBrowser-lr.458 and OB-Morphic-lr.112 are | > | loaded. | > | > | > | > Doing twice a proceed resume the loading. | > | > It then blocks on SHWorkspace, for the very same reason. | > | > | > | > | > | yes.. | > | | > | | > | > After having manually fixed the Nile problem (isInMemory), | Pharo | > | loads | > | > well. ProfStef is open. | > | > | > | > | > | I did the same... | > | | > | | > | > OmniBrowser-lr.469 and OB-Morphic-lr.116 are loaded. This means | > | that | > | > OmniBrowser is loaded twice. Is this the intended behavior? | > | > | > | > | > | I saw directly the final versions: 469 and 116. I didn't notice it | | > was | > | first | > | trying to load 458 and 112. | > | I know that in such conflict, Metacello will load the last one, | > but I | > | didnt | > | know that it actually LOADS also the previous versions. I thought | | > that | > | it | > | only loads the final version, not both of them. In such case, I | > think | > | it is | > | a metacello bug. | > | | > | See this link: | > | | http://groups.google.com/group/metacello/browse_thread/thread/e8a08b3ed1a9b772/edd79873a97a80d9?lnk=gst&q=conflict#edd79873a97a80d9 | > | | > | Dale, can you help us? | > | | > | Thanks | > | | > | Mariano | > | | > | > Alexandre | > | > | > | > | > | > | > | > On 28 Apr 2010, at 11:40, Mariano Martinez Peck wrote: | > | > | > | > | > | >> | > | >> On Wed, Apr 28, 2010 at 3:22 PM, Alexandre Bergel | > | <[email protected]> | > | >> wrote: | > | >> Hi! | > | >> | > | >> I am now trying to make ConfigurationOfPharo load the last | > version | > | of | > | >> OmniBrowser. | > | >> If I do in a fresh core: ConfigurationOfPharo project | lastVersion | > | load | > | >> | > | >> Then OmniBrowser-lr.458 and OB-Morphic-lr.112 are loaded. | > | >> | > | >> | > | >> No. If you take a PharoCore 1.0 OR 1.1 and evaluate | > | ConfigurationOfPharo | > | >> project lastVersion load | > | >> | > | >> It installs OmniBrowser-lr.469 and OB-Morphic-lr.116 | > | >> which are correct as those are defined in | > | ConfigurationOfOmniBrowser | > | >> version 1.1.2. And ConfigurationOfPharo 1.1 has 1.1.2 of OB. | > | >> | > | >> | > | >> The loading blocks on the deprecated warning (yes, the | > registration | > | in the | > | >> World menu). | > | >> In ConfigurationOfPharo>>version11: I have | > | >> | > | >> spec | > | >> project: 'PharoNonCorePackages' | > | with: | > | >> '1.1.0'; | > | >> project: 'NewInspector' with: | > '1.1'; | > | >> project: 'Shout' with: '1.0'; | > | >> project: 'Shout Tests' with: | '1.0'; | > | >> project: 'OCompletion' with: | '1.1'; | > | >> project: 'OCompletion Tests' | with: | > | '1.1'; | > | >> project: 'OB Dev' with: '1.1.3'; | > | >> project: 'OB Dev Tests' with: | > | '1.1.3'; | > | >> ... | > | >> | > | >> I therefore assume that the version 1.1.3 of OmniBrowser is | > | loaded. | > | >> 1.1.3 is indeed the last version specified in | > | ConfigurationOfOmniBrowser: | > | >> ConfigurationOfOmniBrowser project lastVersion | > | >> => ~1.1.3 [ConfigurationOfOmniBrowser] | > | >> | > | >> But I evaluate: ConfigurationOfOmniBrowser project lastVersion | > | load | > | >> Then the version OB-Morphic-lr.116, OB-Standard-lr.463 and | > | >> OmniBrowser-lr.469 are loaded. | > | >> | > | >> | > | >> Exactly. And that's correct. Those are the versions that are | > | defined in | > | >> ConfigurationOfOmnibrowser 1.1.3 | > | >> | > | >> I find it is very hard to keep track of what is actually | loaded. | > | >> | > | >> | > | >> I don't understand your problem. Everything seems to work as | > | exepected. | > | >> | > | >> | > | >> I haven't closely followed the evolution of Metacello, but | > there is | > | not a | > | >> way to say: | > | >> spec project: 'OB Dev' with: 'lastestVersion' | > | >> | > | >> Yes. Don't put any version. If you don't define a version, | > | metacallo will | > | >> load the last one. | > | >> | > | >> project: 'OB Dev'; | > | >> | > | >> or even remove that line from the version method. Even more, | if | > | you want | > | >> ALL the last, you can load the baseline instead of the version. | | > In | > | such | > | >> case, as you don't specify any version, it will download all | the | > | last ones. | > | >> | > | >> Cheers | > | >> | > | >> Mariano | > | >> | > | >> | > | >> Or Something? | > | >> | > | >> Cheers, | > | >> Alexandre | > | >> -- | > | >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: | > | >> Alexandre Bergel http://www.bergel.eu | > | >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. | > | >> | > | >> | > | >> | > | >> | > | >> | > | >> | > | >> _______________________________________________ | > | >> Pharo-project mailing list | > | >> [email protected] | > | >> | > | | http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project | > | >> | > | >> _______________________________________________ | > | >> Pharo-project mailing list | > | >> [email protected] | > | >> | > | | http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project | > | >> | > | > | > | > | > | > _______________________________________________ | > | > Pharo-project mailing list | > | > [email protected] | > | > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo- | > project | > | > | > | > _______________________________________________ | > Pharo-project mailing list | > [email protected] | > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project | | -- | _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: | Alexandre Bergel http://www.bergel.eu | ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
