Hi vitor
thanks for this report. My answers are below and other will surely reply
to you.
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.
which one?
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....
Sometimes smalltalkhub is slow and we have a watch dog that kills it and
restart it.
I opened Monticello and had to Flush Cached Version
What is that? I never saw it.
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:
OSSubProcess is not working on windows so it impacts git use. Do not use
git.
Let us make sure that everything is working well.
We manage moose many many package with MC and pharo itself with
Monticello and it works.
1- Shouldn't I be using Windows? Pharo isn't stable on a Windows
plataform?
I know that on windows there are some instabilities and we should work
on them but not at this level.
2- Is Komiter reliable or should I use Monticello directly?
I just fixed a glitch in Komitter when used from Versionner because I
was annoyed.
Most of the people do not use it and I suggested to remove it because
this is a bad piece of code
but people told me that this is important to be able to cherry pick.
3- Is Smalltalkhub reliable or should I use other repository?
We manage moose many many package with MC and Pharo itself on SmalltalkHub
so it is working. It has some glitches but overall it works and it is
reliable.
Sometimes it is getting slow and we should restart it.
We receive mails when something is going wrong.
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? :(
For the redCross
- we got some regression with FreeType pluggin plugin since spur
-- our current plan is to use uFFI and throw away the plugin code
- it happens that at load time (when you import broken code) we get
an error window
and then when we close it a new UI process stay around and this is
not good.
Thanks in advance and sorry if the stuff I am doing seems dumb... :(
This is not you. I'm sure. I'm a bug attractor so I know the feeling.
Thanks to report any problem you have.
Regards,
Vitor
