Closed pdebruic closed 12 years ago
What version of GemStone are you running on? Also I assume that you've cloned/checkedout the gemstone2.4 branch?
Should the file tree code itself not be loaded by a MCDirectoryRepository? Is the package MonticelloFileTree-Core perhaps a Mcz file in your directory?
I have not thoroughly looked at the most recent docs, but bootstrapping the filetree code itself should be loaded with another monticello repository.
Hth Let us know Otto
On 25 May 2012, at 19:00, Paul DeBruicker reply@reply.github.com wrote:
I've left it running and tried twice in a clean and unmolested extent.
This command run in the stone's workspace never seems to get anywhere:
Gofer new repository: (MCFileTreeRepository new directory: (FileDirectory on: '/opt/git/filetree/repository/')); package: 'MonticelloFileTree-Core'; load.
I can put the extent I'm using up on dropbox if you want to try it yourself.
Reply to this email directly or view it on GitHub: https://github.com/dalehenrich/filetree/issues/28
Oh I see you reported the version and other info in the title ... sorry about that ... also I do assume that you followed the gemstone installation instructions.
I'll be able to take it for a spin soon and see if I can reproduce the problem ...
Its Gemstone 2.4.4.1 from seaside.gemstone.com. I use the installGemstone2.4.sh script from that site to install into /opt. I then update GLASS to 1.0b71. Then I follow the instructions here:
https://github.com/dalehenrich/filetree/blob/master/doc/GemStoneInstall.md
But it worked this time so I'm closing the issue.
I must just be a little impatient today or something.
Sorry for the false alarm.
Third time lucky etc. etc. I'm going to attempt to push my last known good Zinc port from May 2011 to a branch of the Zinc tree here in a bit.
Paul,
I noticed that you forked Sven's version of the zinc repository instead of the glassdb version ... I was expecting that the glassdb repository would be the concentration point for feeding back changes to Sven and the central point for coordinating porting changes ...
BTW, do you have a clue why it took so long the first two times? Or did it eventually finish?
I don't know why it took so long. The third time it also took a while. I just let it keep going. It just seemed out of the ordinary so I made an issue. I'll fix the zinc fork head before I push anything into gtihub
I'm going to reopen, just so that I can take a look at the load time ... I've not noticed it taking long, but I do know that I haven't optimized anything either ...
Its slow because in the instructions on github you use FileDirectory instead of ServerFileDirectory.
If you change:
Gofer new repository: (MCFileTreeRepository new directory: (FileDirectory on: '/opt/git/filetree/repository/')); package: 'MonticelloFileTree-Core'; load.
to:
Gofer new repository: (MCFileTreeRepository new directory: (ServerFileDirectory on: '/opt/git/filetree/repository/')); package: 'MonticelloFileTree-Core'; load.
It loads in a few seconds rather than >30 mins. But I dont know how that change may affect other things.
On 05/25/2012 11:43 AM, Dale Henrichs wrote:
I'm going to reopen, just so that I can take a look at the load time ... I've not noticed it taking long, but I do know that I haven't optimized anything either ...
Reply to this email directly or view it on GitHub: https://github.com/dalehenrich/filetree/issues/28#issuecomment-5937548
Okay! That definitely explains it! Good catch ... I'll update the instructions and then close the issue
updated the gemstone installation instructions on master and gemstone2.4 branchs ... other branches will see the fix when I merge ...
Thanks Paul!
I've left it running and tried twice in a clean and unmolested extent.
This command run in the stone's workspace never seems to get anywhere:
I can put the extent I'm using up on dropbox if you want to try it yourself.