Guido,

If the maintainer of a configuration would like to support bleeding edge loads that propagate through the dependent projects then they should specify which baseline version to use for each dependent project. For Native Boost the entry for AsmJit in the #baseline13: method could be changed to:

������� project: 'AsmJit'
��������� with: [
������������� spec
��������������� className: 'ConfigurationOfAsmJit';
"==>"������� versionString: #bleedingEdge;
��������������� repository: 'http://www.smalltalkhub.com/mc/Pharo/AsmJit/main' ];

Then the bleedingEdge load would be propagated through to the dependents ... but then you'd want the AsmJit configuration modified as well:)

Dale

---

From: "Guido Chari" <charig@gmail.com>
To: pharo-dev@lists.pharo.org
Sent: Wednesday, June 26, 2013 7:27:19 AM
Subject: [Pharo-dev] Metacello doubt

I have a question since i'm trying to create some jenkins job for the first time. Sorry if this was already discussed...

I have a dependency with for example NativeBoost. And i want NativeBoost in its bleedingEdge version. If I "loadBleedingEdge" NativeBoost is on its last version on every package but not its own dependencies as for example AsmJit. Is this the right behavior? How can i express to have not only my dependency but also the dependencies of my dependencies in its bleedingEdge version?