We looked a bit at OSProcess in 2.0 with Mariano on Friday. We tried to have clean loading (i.e., remove FileDirectory references + a couple of other stuff). We also spotted some inconsistencies in the ConfigurationOfOSProcess.
Good!
I'm going to continue what we started but I don't think I will be able to make all the tests pass (if I remember well, they are not passing in 1.4 summer neither...)
Where should I commit the changes?
if you cannot in the os repo you can in the PharoTaskForces but let us wait that david reply. stef
On 04/11/12 11:57, Esteban Lorenzano wrote:
Hi Dale,
On Nov 4, 2012, at 11:51 AM, Dale Henrichs <dhenrich@vmware.com> wrote:
Esteban,
If I'm not mistaken the MetacelloToolBox is a candidate for inclusion to support Versionner.
damn! I didn't though in that :)
If you are getting Github stuff in Pharo2.0, then I am curious which version of Metacello you are using. The #stable version of Metacello doesn't include github.
The github support stuff needs OSProcess and from what I understand OSProcess won't be included in Pharo2.0, so perhaps you are more concerned about the GitHub support than MetacelloToolBox?
no idea, I just checked the latest baseline, and probably not the used one (sunday mode, today :)
I really can't think of anything in MetacelloToolBox that makes it a "bad idea" to include in Pharo2.0.
well.. is not about the toolbox, is about over-bloating the image... but the Versionner needs are a good point for its inclusion :) anyway, the most important thing is to be sure that packages we include and correspond to dev-support are unloadable when you do a shrink for production, and Metacello completelly fulfills that requirement :)
I think that you might be happier if you stuck with 1.0-beta.31.1.5 as that predates the github support.
as I said, this was my mistake on checking the baseline... github is not in current 2.0 images.
Esteabn
Dale
----- Original Message ----- | From: "Esteban Lorenzano" <estebanlm@gmail.com> | To: Pharo-project@lists.gforge.inria.fr | Sent: Sunday, November 4, 2012 2:37:29 AM | Subject: Re: [Pharo-project] How to load MetacelloToolbox | | ConfigurationOfMetacello ... load: 'Metacello-ToolBox'. | | should doit, and the baseline says: | | package: 'Metacello-ToolBox' with: [ spec requires: | #('Metacello-Base' 'Metacello-Core') ]; | | | and the "already included" metacello should be what is in the 'batch' | group (Base and some Github access stuff). | | And I insist, including MetacelloToolBox in the 2.0 core image is a | bad idea... | | Esteban | | On Nov 4, 2012, at 11:31 AM, Camillo Bruni <camillobruni@gmail.com> | wrote: | | > Anyway what would be the default way to install it? | > | > AFAIK I didn't find any reference in the ConfigurationOfMetacello | > but then again I am not particularly at searching :P | > | > On 2012-11-04, at 11:27, Marcus Denker <marcus.denker@inria.fr> | > wrote: | >> On Nov 3, 2012, at 8:34 PM, Dale Henrichs <dhenrich@vmware.com> | >> wrote: | >> | >>> Out of curiosity, what are some of the undeclared references? | >>> | >>> There shouldn't be any undeclared references, unless you ignored | >>> the required packages or ??? offhand I can't imagine what they | >>> might be... | >> | >> | >> I checked the latest 2.0 image and there are no Undeclareds | >> there... | >> | >> With the build server dead (again...) checking of something is | >> destroyed there we need to wait... | >> | >> | >> -- | >> Marcus Denker -- http://marcusdenker.de | >> | >> | > | > | | |
-- http://tulipemoutarde.be CA: +1 778 558 3225 BE: +32 65 709 131