On Thu, Aug 10, 2017 at 11:58 PM, Nicolai Hess <[email protected]> wrote:
> > > Am 10.08.2017 11:21 nachm. schrieb "Guillermo Polito" < > [email protected]>: > > > > On Thu, Aug 10, 2017 at 9:39 PM, Torsten Bergmann <[email protected]> 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" > > > What does "clone using sourcetree" mean? > Yeap, sorry. I meant https://www.sourcetreeapp.com/ It is a free graphical git client from atlassian. In windows I default to graphical tools :). I assume not most of the people will install a msys environment on their machines (but maybe I'm wrong...). > > > 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... > > >> - that #development branch is used instead of master >> > > I'll make another writeup about the entire process. > > >> - how one can keep his own fork up to date >> > > And about this one too > > >> >> Also it would be good to have the AboutBox in Pharo with the build number >> again. >> > >> Because the ZeroCnnf just gives you a Pharo.image and nobody knows what >> the build number >> or sha was to reproduce how old or new this is. >> > > Well, actually right now > > SystemVersion current > > has the hash of the commit the image was generated from if you check the > inspector. It's then a UI problem and easy to fix. Maybe somebody could use > this to try making a pull request? > > Then, we could add a build number in SystemVersion of course. > > Guille > >> >> Thanks >> T. >> >> >> *Gesendet:* Donnerstag, 10. August 2017 um 17:17 Uhr >> *Von:* "Guillermo Polito" <[email protected]> >> *An:* "Discusses Development of Pharo" <[email protected]> >> *Betreff:* [Pharo-dev] Writeup: how to contribute to Pharo >> Hi, >> >> I've made some write up for the pharo part (not metacello or external >> projects) >> >> https://github.com/guillep/PharoIntegrationProcess/wiki/Cont >> ribute-a-fix-to-Pharo >> >> Of course, expect bugs on it :) Not everything is smooth. If you have >> comments, they are welcome. >> >> Guille >> >> -- >> >> >> >> Guille Polito >> >> >> >> Research Engineer >> >> French National Center for Scientific Research - *http://www.cnrs.fr* >> <http://www.cnrs.fr> >> >> >> >> >> >> *Web:* *http://guillep.github.io* <http://guillep.github.io> >> >> *Phone: *+33 06 52 70 66 13 <+33%206%2052%2070%2066%2013> >> > > > > -- > > > > Guille Polito > > > Research Engineer > > French National Center for Scientific Research - *http://www.cnrs.fr* > <http://www.cnrs.fr> > > > > *Web:* *http://guillep.github.io* <http://guillep.github.io> > > *Phone: *+33 06 52 70 66 13 <+33%206%2052%2070%2066%2013> > > > -- Guille Polito Research Engineer French National Center for Scientific Research - *http://www.cnrs.fr* <http://www.cnrs.fr> *Web:* *http://guillep.github.io* <http://guillep.github.io> *Phone: *+33 06 52 70 66 13
