Handy, will try to remember and add to our stripping scripts... Regards, Gary
----- Original Message ----- From: "Adrian Lienhard" <[email protected]> To: <[email protected]> Sent: Monday, October 19, 2009 5:16 PM Subject: Re: [Pharo-project] [update] #10487 > > On Oct 19, 2009, at 18:05 , Gary Chambers wrote: > >> +1 Or at least have a reliable one-click (one message send) way of >> unloading >> the tests cleanly for deployment purposes. > > Check out "ScriptLoader new cleanUpForProduction" > > This is why I detangled the tests and moved them in a modular package > that can be unloaded. With this script, which also clears the MC > ancestory metadata, you get an image with only 6.7MB size on disk. > > Cheers, > Adrian > >> >> Regards, Gary >> >> ----- Original Message ----- >> From: "Lukas Renggli" <[email protected]> >> To: <[email protected]> >> Sent: Monday, October 19, 2009 4:51 PM >> Subject: Re: [Pharo-project] [update] #10487 >> >> >>> Personally I would like to download an image *without* any tests, no >>> matter if this is a core or a dev image. And have included a detailed >>> report on the results of running all the tests in that particular >>> image. >>> >>> Cheers, >>> Lukas >>> >>> 2009/10/19 Damien Cassou <[email protected]>: >>>> 2009/10/19 Mariano Martinez Peck <[email protected]>: >>>>> What I propose is to identify the red tests of Pharo dev and look >>>>> for >>>>> the >>>>> package and ask the maintainers (if there is anyone) to fix it. >>>>> And the >>>>> regarding tests, we can tag them as 1.1 >>>> >>>> Ok. Can you have a look at that please? The problem is that we will >>>> also have to maintain these tests. >>>> >>>> >>>>>>> Moreover, if packages are included in Pharo dev it is because >>>>>>> it is a >>>>>>> Pharo decision. So, if pharo thinks that, for example, >>>>>>> ocompletion >>>>>>> must be in Pharo, so, I think that ocompletion tests must be >>>>>>> green. >>>>>> >>>>>> But I don't think that the package lists (web and dev images) are >>>>>> blessed by the Pharo board. >>>>>> >>>>> And I am not agree with this also. I think Pharo board, and even >>>>> the >>>>> community has to choose the Pharo packages. Please, take in mind >>>>> that >>>>> the >>>>> final users will use and see Pharo, NOT PHARO CORE. >>>> >>>> I confirm. The Pharo user community has the last word on what gets >>>> integrated into images I generate, not me. The list of packages is >>>> at: >>>> http://code.google.com/p/pharo/wiki/Packages. >>>> >>>> -- >>>> Damien Cassou >>>> http://damiencassou.seasidehosting.st >>>> >>>> "Lambdas are relegated to relative obscurity until Java makes them >>>> popular by not having them." James Iry >>>> >>>> _______________________________________________ >>>> Pharo-project mailing list >>>> [email protected] >>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>>> >>> >>> >>> >>> -- >>> Lukas Renggli >>> http://www.lukas-renggli.ch >>> >>> _______________________________________________ >>> 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
