Pharo Issue 14080 Affects Metacello

https://pharo.fogbugz.com/default.asp?14080

I included the MetaC packages in the slice and committed to the 50 Inbox. Was that correct?

Sean P. DeNigris wrote

https://pharo.fogbugz.com/default.asp?14080

Disregard message: My head was spinning a bit after 8 slice versions. The final changes to Metacello turned out to insignificant, so I dropped them from the slice altogether

Sean P. DeNigris wrote

I included the MetaC packages in the slice and committed to the 50 Inbox. Was that correct?

Although my question still stands in general. Is it okay to commit MetaC packages directly to Pharo?

What is the MetaC package and how does it affect Metacello?

Dale

On 4/28/15 12:36 PM, Sean P. DeNigris wrote:
--
You received this message because you are subscribed to the Google Groups "Metacello" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/d/optout.

Dale Henrichs-3 wrote

What is the MetaC package and how does it affect Metacello?

Dale, I ended up backing out the change, but I wanted to clarify whether in general it's okay to patch the the Metacello integrated in Pharo via slice, or do we handle via config or what.

Ah ... I think that in Pharo4.0 and before, the slice is the only way,
since the code was not being managed by configs in the base and fixes on
github were not being slip-streamed into the builds ..

For Pharo5.0 I think that the plan is for Pharo to slip-stream the
latest master branch version into builds, so once that mechanism is in
place the fixes should be introduced on github so that the travis
tests,etc. remain consistent ...

Dale

On 5/28/15 1:52 PM, Sean P. DeNigris wrote:
--
You received this message because you are subscribed to the Google Groups "Metacello" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/d/optout.