[Pharo-project] why does monticello updates accessing web when i save on dir?
Saving packages in my local directory repository and then copying them to the squeaksource is my pattern of work since Squeak. But, when I apply that pattern, Pharo accesses web everytime i save a version taking long time. Is this behavior have some meaning or is it some sort of side effect? Best Regards -- View this message in context: http://forum.world.st/why-does-monticello-updates-accessing-web-when-i-save-... Sent from the Pharo Smalltalk mailing list archive at Nabble.com.
Does it access the web when you store to your local repo or when you copy to SqueakSource? Was that different with Squeak? If there's some unnecessary "activity" I would be interested to know about ;) Cheers, Adrian On Jan 25, 2011, at 14:44 , HwaJong Oh wrote:
Saving packages in my local directory repository and then copying them to the squeaksource is my pattern of work since Squeak. But, when I apply that pattern, Pharo accesses web everytime i save a version taking long time. Is this behavior have some meaning or is it some sort of side effect?
Best Regards -- View this message in context: http://forum.world.st/why-does-monticello-updates-accessing-web-when-i-save-... Sent from the Pharo Smalltalk mailing list archive at Nabble.com.
It accesses the web when i store to my local repo. Since my last post here, I am coming up with a suspicion that it may have some package dependency toward the web. I better check. Your interest tell me, it is not a usual case. It is interesting to me, too. :-) -- View this message in context: http://forum.world.st/why-does-monticello-updates-accessing-web-when-i-save-... Sent from the Pharo Smalltalk mailing list archive at Nabble.com.
At some point it tries to refresh all know repositories.. probably to show you the warning "Oh, but there is more recent version of the package you saving.. maybe you need to merge with it before saving" I think this message could be made optional and turned off for "professionals" :) On 25 January 2011 15:25, HwaJong Oh <daliot.oh@gmail.com> wrote:
It accesses the web when i store to my local repo. Since my last post here, I am coming up with a suspicion that it may have some package dependency toward the web. I better check.
Your interest tell me, it is not a usual case. It is interesting to me, too. :-) -- View this message in context: http://forum.world.st/why-does-monticello-updates-accessing-web-when-i-save-... Sent from the Pharo Smalltalk mailing list archive at Nabble.com.
-- Best regards, Igor Stasenko AKA sig.
Do you mean #checkForNewerVersions with the message 'CAUTION! These versions in the repository may be newer:'? At least in PharoCore 1.1.1 this method doesn't have a sender. Adrian On Jan 25, 2011, at 15:49 , Igor Stasenko wrote:
At some point it tries to refresh all know repositories.. probably to show you the warning "Oh, but there is more recent version of the package you saving.. maybe you need to merge with it before saving" I think this message could be made optional and turned off for "professionals" :)
On 25 January 2011 15:25, HwaJong Oh <daliot.oh@gmail.com> wrote:
It accesses the web when i store to my local repo. Since my last post here, I am coming up with a suspicion that it may have some package dependency toward the web. I better check.
Your interest tell me, it is not a usual case. It is interesting to me, too. :-) -- View this message in context: http://forum.world.st/why-does-monticello-updates-accessing-web-when-i-save-... Sent from the Pharo Smalltalk mailing list archive at Nabble.com.
-- Best regards, Igor Stasenko AKA sig.
Why on earth does Pharo thinks me as professional? I am not at that level yet. :-) So the waiting is needed for saver save. I should endure this, but I makes harder for my micro commit habbit. I try to commit as small as refactoring operation defined in the book "Refactoring-M. Fowler" so the reader of my code will clearly see the change. The commit cycle 1. refactor 2. run test 3. read package change 4. commit with comment with refactoring name followed by extra info: "ExtractMethod: #refreshLayoutsFor: " The waiting distracts my focus applying this. Best Regards -- View this message in context: http://forum.world.st/why-does-monticello-updates-accessing-web-when-i-save-... Sent from the Pharo Smalltalk mailing list archive at Nabble.com.
Why on earth does Pharo thinks me as professional? I am not at that level yet. :-) So the waiting is needed for saver save. I should endure this, but I makes harder for my micro commit habbit. I try to commit as small as refactoring operation defined in the book "Refactoring-M. Fowler" so the reader of my code will clearly see the change. The commit cycle 1. refactor 2. run test 3. read package change 4. commit with comment with refactoring name followed by extra info: "ExtractMethod: #refreshLayoutsFor: " The waiting distracts my focus applying this. Best Regards -- View this message in context: http://forum.world.st/why-does-monticello-updates-accessing-web-when-i-save-... Sent from the Pharo Smalltalk mailing list archive at Nabble.com.
if you save locally did you try to psuh the changes with gofer Gofer new ... ; push On Jan 25, 2011, at 2:44 PM, HwaJong Oh wrote:
Saving packages in my local directory repository and then copying them to the squeaksource is my pattern of work since Squeak. But, when I apply that pattern, Pharo accesses web everytime i save a version taking long time. Is this behavior have some meaning or is it some sort of side effect?
Best Regards -- View this message in context: http://forum.world.st/why-does-monticello-updates-accessing-web-when-i-save-... Sent from the Pharo Smalltalk mailing list archive at Nabble.com.
participants (4)
-
Adrian Lienhard -
HwaJong Oh -
Igor Stasenko -
Stéphane Ducasse