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 things like filetree (and gitfiletree, where it has a special way to interact with git). The problem is that MC is very strict with dependencies; it is one of the very few code paths where MC check not only the version number and author of a package, but also it's UUID.
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 number - but I guess you could use it for other purposes with any random issue number or 00000. cheers -ben
I guess yes. But just make sure you don't save it in Pharo inbox ;) Thierry
On Wed, Apr 29, 2015 at 8:18 PM, Sean P. DeNigris <sean@clipperadams.com <mailto:sean@clipperadams.com>> wrote:
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 those packages with it.
----- Cheers, Sean -- View this message in context: http://forum.world.st/Understanding-Slices-tp4822860p4822867.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.