On 18.03.2010 01:09, Germán Arduino wrote:
I would like to help also, even when I'm with very little free time.
To start I would like to understand how is the Pharo development
process, being that (until now) I've mostly used RC2/3.
The main doubts I've are:
1. The UNSTABLE version (the 1.1 right?) comes with no dev tools
installed (OB, Shout, etc). Exist some metacello configuration to
install all these tools? (I thinked that could be
ConfigurationOfPharo, but seems that fail to install).
Not all dev tools can be expected to be updated and work on a
work-in-progress core image, thus we (well, at least I) make due with
the good ol' system browser.
Important packages will be updated and configurations working in 1.1
made available after API changes have been prohibited.
That said, the O2Browser was updated a short time ago to work in 1.1
IIRC, your best bet for a more advanced browser would probably be to try
and load a configuration of that.
2. On the gforge page (http://gforge.inria.fr/frs/?group_id=1299),
what is Pharo (pharo-dev) ? Is 1.0 RC2 with some tools?
Pharo-dev is older versions of the core image, with tools equivalent to
what is found in the RC-releases preloaded. (In fact, the latest release
in that category is Pharo1.0-10508-rc2dev10.01.2.zip )
3. On the gforge page (http://gforge.inria.fr/frs/?group_id=1299),
what is Pharo1.1-64bit-Core? I mean, with which vm is supposed to be
used?
It's an image that has been run through the SystemTracer which converts
it to 64bit format.
You will be able to run it on the 64-64 version of the 5.0 Mac OSX VM's,
not sure about the other platforms.
Please note many of the vm-plugins are not 64bit clean, thus are likely
to fail or crash your VM if used.
4. Some days ago I asked (with no response) about the Package Browser
on RC2. I've found several mails talking about some problems between
OB and O2, but I've not clear how to install it (I would like to have
on 1.1 also).
AFAIK, Alexandre and David spent some time a while ago to completely
separate the model of O2 from that used by OB, thus resolving clashes
caused by O2 overrides, now both should be able to be loaded at the same
time in 1.0.
(load with ConfigurationOfO2 in MetacelloRepository)
Well, this is all for now, I will try also to read on the web page
about repos and other things related with the Pharo development
process.
Thanks.
Germán.
There's only two repo's you really need:
MetacelloRepository, for loading the tools you find useful (Really nice
for checking issues with different tools in 1.1 as well)
Inbox - Where you commit slices for inclusion in the next version.
Cheers,
Henry
PS. The latest 1.0 release is PharoCore-1.0-10515rc3 (available from the
gforge page), to get the equivalent of a Pharo (pharo-dev) rc image,
load the ConfigurationOfPharo into that, and evaluate
(ConfigurationOfPharo version: '1.0-rc.3-baseline') load.
PPS. There will be an error when doing the load, since the AST-Tests
package in squeaksource/rb has been renamed AST-Tests-Core, and the same
for Refactoring-Tests, and the old packages removed...
Lukas, would you mind uploading them again?
For now, you can debug, and in the method that breaks, change the
packageSpec's file to 'AST-Tests-Core-lr.8' and
Refactoring-Tests-Core-lr.34 respectively.
This will happen twice, since the spec first loads
ConfigurationOfRefactoringBrowser once as part of the defined packages,
then again as a prereq when loading ConfigurationOfOmniBrowser.
<file:///C:/Pharo/Pharo1.0-10508-rc2dev10.01.2/Pharo1.0-10508-rc2dev10.01.2/Fonts/>
_______________________________________________
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
