I understood. Thanks for the answer Dale. The drawback in this case is to
specify a particular dependency to AsmJit in my configuration. Also,
perhaps is the right way since i realized i have a particular dependency on
it.

But this discussion makes me thing a little and so i have a new question.

Form what I (mis) undestand from Metacello, when asking for a bleedingEdge
version it loads only the baseline that specifies packages and then last
version of every package specified there.

As in the projects referenced on the baseline there is no need for
specifying a version, and that's the case of nativeBoost configuration,
wouldn't it be interesting to have some behavior (i mean i new method for
loading like loadDeepSymbolic:) that not only load the symbolicVersion of
the package asked, but also propagate that symbolicVersion (bleedingEdge in
this case) to all the dependencies that don't specify a concrete version?

Guido.


2013/6/26 Dale K. Henrichs <dale.henri...@gemtalksystems.com>

> 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" <cha...@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?
>
>
>
>
>
>

Reply via email to