Evan
pay attention at Metacello is complex and may be it would be simpler for
you to use Versionner.
Stef
On 4/8/14 21:15, Evan Donahue wrote:
Hello,
I am working on getting a project into Monticello, and I am trying to
understand the difference between letting Monticello handle package
dependencies and setting up a metacello configurationOf class. In
particular:
PBE2 describes a technique of adding a MyProject-All package that
requires MyProject-Core and MyProject-Tests (for example) so that one
need only save and load MyProject-All and the others will come along
for the ride.
I'm confused because I do not remember writing that. So I would not do it.
I have gotten this to work and it seems like a straightforward
approach for a simple project. My question, then, is how does a
Metacello ConfigurationOf differ from this approach for the simple
core + tests project described? Here are a couple of my points of
confusion, but it may be that they can all be answered with one
concise statement:
1) If I set up a ConfigurationOf, can that replace the MyProject-All
package for saving and loading the whole project at once, or are they
complimentary techniques?
You do not need the project-all
2) Is the Monticello action-click >> add required package necessary if
one specifies dependencies in the ConfigurationOf?
No
This is totally orthogonal.
Would they cause problems if they went out of sync with the
dependencies described in the ConfigurationOf?
3) Do I correctly infer that the proper way to use a ConfigurationOf
is to give it no dependencies, load it from the project repository on
its own, and then run its project load message to have it import the
rest of the project?
Just watch the versionner video and use versionner because in a couple
of click you get get a configurationOf up and running.
If there are any particularly good resources describing the use of
Metacello beyond PBE2, please let me know. In the meantime, I'll keep
searching and experimenting.
50 pages is not enough... It was boring to write :)
Thanks,
Evan
