Le 29/04/2015 15:17, Ben Coman a écrit :
Someone correct me - any package can have a dependent package added.
We just don't do that (I've never seen it my past couple of years
with Pharo).
You're right. We do have packages with dependencies floating in places,
with dedicated handling for thing
Great, thanks for the answers!
Someone correct me - any package can have a dependent package added. We
just don't do that (I've never seen it my past couple of years with
Pharo). A Slice is simply an empty package that has dependencies. Now it
seems somewhat tied to development of the Pharo image since it requires an
issue numb
Sergio Fedi wrote
> Are Slices a way to represent a change accross packages?
Exactly. In the MC browser, there is a button to create a slice from an
issue number. During that workflow, you will be asked to select all relevant
packages. When the slice is committed or loaded, it will bring all of th
Are Slices a way to represent a change accross packages?
For example, if I add a new functionality, then at least two packages will
be modified.
The one the feature is imlpemented in, and the one with the tests for that
feature.
So a Slice could encapsulate these changes to both packages in a si
