On Wed, Jul 25, 2012 at 1:25 PM, Camillo Bruni <[email protected]>wrote:
> > On 2012-07-25, at 14:10, Patrik Sundberg wrote: > > > Hi, > > > > Is there a way to see the diffs (in terms of changes to image) between > one > > 2.0 build number and another? I don't see any obvious link on the CI > server > > to it, and the github export seems to be done in a way that makes the > diffs > > enourmous. > > you can use the git repos and filter out non-st methods: > git diff $VERSION_A $VERSION_B -- $(git diff --name-only $VERSION_A > $VERSION_B | grep .st) > > Ok, I'll try that. I haven't looked at it more closely, but how come the diffs get so HUGE? is there any easy wins to get more "proper" diffs? > If not, is there a way to do it in image? I can only see changes for > > individual MC packages, not a more system level diff to see exactly what > > changed from one build to another. > > We should have a global Pharo MC Package which has all other packages as > dependencies, that would simplify quite a few things here... > > Otherwise you're stuck with downloading the image for a specific version > which might be corrupted, and thus leaves you without any chance of > inspecting the changes... > > Right, a fully packetized system with meta-packages would seem ideal.
