LoadOrder Test for gemstone AND pharo - Seaside Issue 385

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

LoadOrder Test for gemstone AND pharo - Seaside Issue 385

Torsten Bergmann
Hi all,

see http://code.google.com/p/seaside/issues/detail?id=385 for details
and code is in "LoadOrderTests-tbn.21.mcz" on squeaksource/Seaside29

This is necessary since we want to allow easy testing of latest
seaside code in pharo just by evaluating

    "ScriptLoader loadSeaside29"

from within a pharo image. I hope this is OK for gemstone too since
for non-pharo it keeps the old comanche packages. Anyone able
to confirm this?

Thanks
Torsten


-------- Original-Nachricht --------
> Datum: Wed, 27 May 2009 20:42:41 +0200
> Von: Lukas Renggli <[hidden email]>
> An: Torsten Bergmann <[hidden email]>
> CC: [hidden email], [hidden email]
> Betreff: Re: Seaside29 repository access to fix issue 385

> Hi Torsten,
>
...

>
> > Looks like "LoadOrderTest" is currently more Squeak oriented, but
> > with this patch it should easily work also in pharo.
>
> Keep in mind that this is a script written by the GemStone guys for  
> testing dependencies between packages and their respective tests. I am  
> not sure if it is supposed to be used to load Seaside into Squeak/Pharo.
>
> Cheers,
> Lukas
>
> --
> Lukas Renggli
> http://www.lukas-renggli.ch

--
Neu: GMX FreeDSL Komplettanschluss mit DSL 6.000 Flatrate + Telefonanschluss für nur 17,95 Euro/mtl.!* http://portal.gmx.net/de/go/dsl02

_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Reply | Threaded
Open this post in threaded view
|

Re: LoadOrder Test for gemstone AND pharo - Seaside Issue 385

Dale

----- "Torsten Bergmann" <[hidden email]> wrote:

| Hi all,
|
| see http://code.google.com/p/seaside/issues/detail?id=385 for details
| and code is in "LoadOrderTests-tbn.21.mcz" on squeaksource/Seaside29
|
| This is necessary since we want to allow easy testing of latest
| seaside code in pharo just by evaluating
|
|     "ScriptLoader loadSeaside29"
|
| from within a pharo image. I hope this is OK for gemstone too since
| for non-pharo it keeps the old comanche packages. Anyone able
| to confirm this?

Torsten,

Your change shouldn't be a problem for GemStone ... I've commented with more detail on issue 385.

Dale

_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project