Hello Vitor

2016-08-25 23:16 GMT-03:00 Vitor Medina Cruz <vitormcruz@gmail.com>:
Hello,

I am doing some katas and challenges using pharo 5, and I got a bad impression from the VCS and Project management as a whole. I got a bunch of problems with, as it seems to me, simple stuff, and so I loose a lot of confidence with the system :( I get myself saving the image a lot and double checking anything done with version control. I am going to tell more or less what I have done in the last days for you to get an idea of the problems I had and then ask some questions.

I am using Pharo 5 in a Windows 10 system and I was first trying to use GIT as the underlying provider for monticello. I know gitfiletree has problems in a windows system, but I tried to use it anyway to see what happens and I got an image unusable, with Nautilus package view messed up with red blocks and yellow crosses.... scary. I am not sure if that problem with Nautilus was actually caused by gitfiletree since I changed the package of the configuration of my project (I did that only to see if I could) and then rolled that back while testing gitfiletree... but, well, gitfiletree do not work on Windows, I got an index out of bounds exception or something like that, so I gave up and used filetree with a git client to make actual commits.��

However, for anyone to load my configurations and projects, I could not use filetree with a local directory, so I created a smalltalkhub repository and started to commit there and on my local filetree directory. I used Kommiter to commit onto smalltalkhub and Monticello to copy changes to my local file tree until I got and error using Komiter. I tried to proceed instead of abort and one of the packages didn't commit correctly. Trying to access it on the smalltalkhub site I got an error....

Maybe you mean Versionner? There is an issue in Pharo 5. Quick fix:

KomStagingArea>>remotes

������ self packages isEmpty
������ ������ ifFalse: [
������ ������ ������ | result |������
������ ������ ������ result := self packages first remotes.
������ ������ ������ self packages allButFirst do: [ :each |
������ ������ ������ ������ result := result intersection: each remotes ].
������ ������ ������ ^ result collect: [ :each | each koRemote ] ].
������ ^ Array empty.

��
I opened Monticello and had to Flush Cached Version so that it stopped to tell me that there were no changes and started to prompt an error message. I had to forcibly save a new version so that it work again. If I go now to smalltalkhub, sometimes I got errors, sometimes don't. I don't know yet if the error was with komiter, smalltalkhub or my image.

Oh, and Monticello sometimes says there are changes to pakages that I haven't changed, when I click on changes it discover that there are no changes and remover the "*" mark of it.

I tried using Versioner too, but sometimes when I try to commit a minor version, for example, the system hangs and I need to "Alt + .". For now the reliable way of using versioner is to create a release version and commit from Monticello

Right now I fell like stepping in a land mine, so I would like to know:

1- Shouldn't I be using Windows? Pharo isn't stable on a Windows plataform?

Using Pharo 5 in Windows has some issues, I think most Pharoers are using Mac and Linux.
��
2- Is Komiter reliable or should I use Monticello directly?

I think you should use Versionner, with the fix above in Pharo 5.
��
3- Is Smalltalkhub reliable or should I use other repository?

Sometimes it hangs :(
��

Hern��n

4- I don't believe those problems are normal, otherwise there wouldn't be so many places using Pharo for production purpose, any hints of what I may be doing wrong? :(

Thanks in advance and sorry if the stuff I am doing seems dumb... :(

Regards,
Vitor