Hi,
I'm trying to make MVC version of Squeak 3.8. I did make almost successul result but I have 8MB of changes file. How can I remove this history of change? It seems that Method Dictionary like thing have these history. Can anyone let me know how can I remove all these history? Thanks in advance. |
> I'm trying to make MVC version of Squeak 3.8. I did make almost
> successul result but I have 8MB of changes file. How can I remove > this history of change? It seems that Method Dictionary like thing > have these history. Can anyone let me know how can I remove all these > history? Thanks in advance. Smalltalk condenseChanges -- Lukas Renggli http://www.lukas-renggli.ch |
Hi,
I might have done something wrong, but after condenseChanges and condenseSources the size of sources file increased as much as changes file. Yes, the changes file is 4k now but total size is not decreased. On Jan 13, 2006, at 6:07 PM, Lukas Renggli wrote: >> I'm trying to make MVC version of Squeak 3.8. I did make almost >> successul result but I have 8MB of changes file. How can I remove >> this history of change? It seems that Method Dictionary like thing >> have these history. Can anyone let me know how can I remove all these >> history? Thanks in advance. > > Smalltalk condenseChanges > > -- > Lukas Renggli > http://www.lukas-renggli.ch > |
> I might have done something wrong, but after condenseChanges and
> condenseSources the size of sources file increased as much as changes > file. Yes, the changes file is 4k now but total size is not decreased. #condenseChanges just removes the version history from the changes-file, so if you have accepted the same method twice it just keeps the last version. This should decrease the size of your changes-file. #condenseSources is something completely different. I guess there is no reason that someone wants to do this on its own, unless they are releasing Squeak 4.0, that (probably) will be shipped with a new source-file. This will not change the total size of the changes- plus the sources-file, as the changes will be moved to the source. I am not sure, if everything I wrote here is correct, this is just what I think these methods do. I need to do a #condenseChanges from time to time to reduce the size of the changes-file, because it reaches its limits; but I've never done a #condenseSources. Lukas -- Lukas Renggli http://www.lukas-renggli.ch |
Even though after running condenseChanges, I do have multiple
versions of some method. (I can see this with VersionBrowser). Thanks anyway. I'll try more. On Jan 16, 2006, at 2:24 AM, Lukas Renggli wrote: >> I might have done something wrong, but after condenseChanges and >> condenseSources the size of sources file increased as much as changes >> file. Yes, the changes file is 4k now but total size is not >> decreased. > > #condenseChanges just removes the version history from the > changes-file, so if you have accepted the same method twice it just > keeps the last version. This should decrease the size of your > changes-file. > > #condenseSources is something completely different. I guess there is > no reason that someone wants to do this on its own, unless they are > releasing Squeak 4.0, that (probably) will be shipped with a new > source-file. This will not change the total size of the changes- plus > the sources-file, as the changes will be moved to the source. > > I am not sure, if everything I wrote here is correct, this is just > what I think these methods do. I need to do a #condenseChanges from > time to time to reduce the size of the changes-file, because it > reaches its limits; but I've never done a #condenseSources. > > Lukas > > -- > Lukas Renggli > http://www.lukas-renggli.ch > |
You should have at most two versions, one in the sources file and one
in the changes file. If you have more, then condenseChanges did not work properly. One particular thing that breaks when running condenseChanges is overrides, which relies on the method history in the changes file. Attached is a fix for that, it preserves method histories for methods in a "*-override" category. It's pretty dumb, retaining each and every version of that method. An improvement would be to only keep the necessary ones, that is, those most recent after the categorization changed. But it works ;-) - Bert - Am 16.01.2006 um 04:10 schrieb Sungjin Chun: > Even though after running condenseChanges, I do have multiple > versions of some method. (I can see this with VersionBrowser). > Thanks anyway. I'll try more. > > On Jan 16, 2006, at 2:24 AM, Lukas Renggli wrote: > >>> I might have done something wrong, but after condenseChanges and >>> condenseSources the size of sources file increased as much as >>> changes >>> file. Yes, the changes file is 4k now but total size is not >>> decreased. >> >> #condenseChanges just removes the version history from the >> changes-file, so if you have accepted the same method twice it just >> keeps the last version. This should decrease the size of your >> changes-file. >> >> #condenseSources is something completely different. I guess there is >> no reason that someone wants to do this on its own, unless they are >> releasing Squeak 4.0, that (probably) will be shipped with a new >> source-file. This will not change the total size of the changes- plus >> the sources-file, as the changes will be moved to the source. >> >> I am not sure, if everything I wrote here is correct, this is just >> what I think these methods do. I need to do a #condenseChanges from >> time to time to reduce the size of the changes-file, because it >> reaches its limits; but I've never done a #condenseSources. >> >> Lukas ClassDescription-fileOutChangedMessagesonmoveSourcetoFile.st.gz (826 bytes) Download Attachment |
This issue has been moved to the Mantis database and should be followed
up at http://bugs.impara.de/view.php?id=2514 In the future please post all new issues on the Mantis server at http://bugs.impara.de/ Ken On Mon, 2006-01-16 at 10:49 +0100, Bert Freudenberg wrote: > You should have at most two versions, one in the sources file and one > in the changes file. If you have more, then condenseChanges did not > work properly. > > One particular thing that breaks when running condenseChanges is > overrides, which relies on the method history in the changes file. > > Attached is a fix for that, it preserves method histories for methods > in a "*-override" category. It's pretty dumb, retaining each and > every version of that method. An improvement would be to only keep > the necessary ones, that is, those most recent after the > categorization changed. But it works ;-) > > - Bert - > > Am 16.01.2006 um 04:10 schrieb Sungjin Chun: > > > Even though after running condenseChanges, I do have multiple > > versions of some method. (I can see this with VersionBrowser). > > Thanks anyway. I'll try more. > > > > On Jan 16, 2006, at 2:24 AM, Lukas Renggli wrote: > > > >>> I might have done something wrong, but after condenseChanges and > >>> condenseSources the size of sources file increased as much as > >>> changes > >>> file. Yes, the changes file is 4k now but total size is not > >>> decreased. > >> > >> #condenseChanges just removes the version history from the > >> changes-file, so if you have accepted the same method twice it just > >> keeps the last version. This should decrease the size of your > >> changes-file. > >> > >> #condenseSources is something completely different. I guess there is > >> no reason that someone wants to do this on its own, unless they are > >> releasing Squeak 4.0, that (probably) will be shipped with a new > >> source-file. This will not change the total size of the changes- plus > >> the sources-file, as the changes will be moved to the source. > >> > >> I am not sure, if everything I wrote here is correct, this is just > >> what I think these methods do. I need to do a #condenseChanges from > >> time to time to reduce the size of the changes-file, because it > >> reaches its limits; but I've never done a #condenseSources. > >> > >> Lukas > > signature.asc (196 bytes) Download Attachment |
Free forum by Nabble | Edit this page |