On Mon, Apr 5, 2010 at 5:12 PM, zekUs <zekzekus@gmail.com> wrote:
thanks for reply. it works now.�

so we must take look at configuration packages before loading the package. i am getting used to this metacello system slowly.


Yes. If the "default" doesn't satisfy your needs, then yes. There is no need to explicitly look the code. You can just inspect for example:

(ConfigurationOfO2� project version: '1.2') groups

Then, you can inspect a particular group, and inspect the result of the message "includes" to see what it is included in such group.

Hope this helps.

Cheers

Mariano

2010/4/5 Mariano Martinez Peck <marianopeck@gmail.com>

But that's not what you want. That's why I told you to install it in this way:


�� Gofer new
��� ��� squeaksource: 'MetacelloRepository';
��� ��� package:'ConfigurationOfO2';
��� load.
���
��� �((Smalltalk at: #ConfigurationOfO2) project version: '1.2') load: 'Dev'.


In metacello you can define groups of packages. When you load something with Metacello, you can do just load and that will load the default packages. But after, you can have differents groups. The default can be just the core packages. Then you can have groups called "Dev" where it also installs the dev tools.

Using load:� you specify a group name, a package name or a list.

Take a look at the class ConfigurationOfO2, to the baseline methods, at the end, where the groups are defined.

Moreover, I recommend you to read the Metacello tutorial:�

http://code.google.com/p/metacello/wiki/Tutorial

Cheers

Mariano
_______________________________________________

_______________________________________________
Pharo-users mailing list
Pharo-users@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users