On 22.10.2008, at 22:01, John M McIntosh wrote:
I note I downloaded the current pharo image/changes for pushing out
on the iPhone and
noticed the changes was 10.5MB, but if I condense it becomes 4.2MB
which is much easier to
deal with if I include it in an iPhone.app
Yes, the changes file starts to bug me, too. Especially as we will hit
the 32MB wall at some
point.
I'm wondering here if you need to push out the changes with all the
method versions in it, or
should it be condenced first and rely on changes from MC to show the
history of how the methods
evolved?
mcz seems to be a bit too cumbersom... they get very large very fast,
and then it's very slow
to unpack all of them.
I think we should make a file-system based solution: the history
browser should just look into
a directort ClassName/methodName/ and then show all the files there
(named by timestamp).
Later one can even simply make a web-server based solution: http-get
to a server for all the history.
I love .changes as a changelog, this we should keep. But any release
done (even the intermediate ones)
should come with an empty log.
Marcus
--
Marcus Denker -- [EMAIL PROTECTED]
http://www.iam.unibe.ch/~denker
_______________________________________________
Pharo-project mailing list
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
