2017-08-10 18:20 GMT-03:00 Guillermo Polito <guillermopol...@gmail.com>:
> > > On Thu, Aug 10, 2017 at 9:39 PM, Torsten Bergmann <asta...@gmx.de> wrote: > >> Hi Guille, >> >> nice writeup and definitely needed. Thanks a lot! >> >> If possible you should complete it with: >> - how Windows users could contribute >> > > Hard topic. I'm taking benefit of my gf's windows computer right now to > test. Basically, windows has problems with long paths but there are > workarounds. Icerberg works by default without any changes (same bugs as in > linux and osx at least :)). Here are my notes to make it work: > > * Download latest pharo: > - http://files.pharo.org/image/70/latest-32.zip > - http://files.pharo.org/vm/pharo-spur32/win/stable-20170720.zip > > * Clone using sourcetree > This is very slow and failed to checkout (not clone) because of the > "Filename too long errors" > > I found for this the following workaround: http://pingec.si/blog/ > articles/msysgit-longpath/ > > Once I did that, sourcetree worked nicely, and I could commit and change > branches using iceberg. > > Warning: I did not test making changes on the "long files" to see what > happens... > I tested it on Windows with msysgit. First you have to make the git clone $ git clone https://github.com/hernanmd/pharo.git You have to ***let it fail*** ... "fatal: unable to checkout working tree" ... Then $ cd pharo/ $ git config core.longpaths true $ git checkout -f HEAD Checking out files: 100% (107983/107983), done. Your branch is up-to-date with 'origin/development'.