October 2017 - Pharo-users - lists.pharo.org

Re: [Pharo-users] Pharo 6.1

by Marcus Denker

What actually happens is that moving (with the finder) a file to /Applications removes the com.apple.quarantine flag. you could try: xattr -d com.apple.quarantine <file> (this is related to signing, too, but not the signing of the app, but the container the files are downloaded. We need to use .dmg files and sign them on the build server). Marcus > On 31 Oct 2017, at 15:35, Todd Blanchard <tblanchard(a)mac.com> wrote: > > Actually, it is in Applications > > Sent from the road > >> On Oct 31, 2017, at 02:34, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >> >> >> >>> On 30 Oct 2017, at 20:30, Todd Blanchard <tblanchard(a)mac.com> wrote: >>> >>> I was just preparing a similar post. Just downloaded latest Pharo 6.1-64 for Mac >>> >>> I was greeted with a walkback when it failed to create directory /private/var/folders/ks/wg6l98bj64q6hgvs23wwqypr0000gn/T/AppTranslocation/DAA5EA3A-374D-4ADE-9E04-BBB7433BB6C8/d/Pharo6.1-64.app/Contents/Resources/pharo-local >>> >>> Definitely not the right directory to resolve pharo-local to. >> >> not related :) >> this is because you didnât put Pharo under /Applications as indicated when you download Pharo. >> at the same time, this is because we are still not signing Pharo, then apple moves it to a sandbox, which is bad. I have in my TODO signing the apps, but still no time to do it :/ >> >> Esteban >> >>> >>> -Todd Blanchard >>> >>>> On Oct 30, 2017, at 12:27 PM, ÐÐ¸ÐºÐµÐ½ÑÐ¸Ð¹ ÐÐ¾ÑÐ°Ð¿Ð¾Ð² <vikenti.potapov(a)gmail.com> wrote: >>>> >>>> >>>> I've just downloaded Pharo 6.1 from pharo.org, unzipped it and started. And i've got an error: >>>> "UTF8InvalidText: Invalid utf8 input detected" >>>> >>>> Whether i save image or not, every time i start it i get the same error. >>>> >>>> System: win 7 professional x64 on 6-core Athlon Phenom. >>>> Locale: russian (cyrillic). >>>> >>>> Can i fix it by myself or i should forget about 6.1 until global bugfix? >>>> >>>> Vikenti Potapov >>>> >>> >>> >> >> >

Oct. 31, 2017

Re: [Pharo-users] Pharo 6.1 - Apple signing

by Andrew Glynn

If it would be a help, I can sign the apps. Cheers Andrew From: Todd Blanchard Sent: Tuesday, October 31, 2017 10:36 AM To: Any question about pharo is welcome Subject: Re: [Pharo-users] Pharo 6.1 Actually, it is in Applications Sent from the road > On Oct 31, 2017, at 02:34, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > > >> On 30 Oct 2017, at 20:30, Todd Blanchard <tblanchard(a)mac.com> wrote: >> >> I was just preparing a similar post. Just downloaded latest Pharo 6.1-64 for Mac >> >> I was greeted with a walkback when it failed to create directory /private/var/folders/ks/wg6l98bj64q6hgvs23wwqypr0000gn/T/AppTranslocation/DAA5EA3A-374D-4ADE-9E04-BBB7433BB6C8/d/Pharo6.1-64.app/Contents/Resources/pharo-local >> >> Definitely not the right directory to resolve pharo-local to. > > not related :) > this is because you didnât put Pharo under /Applications as indicated when you download Pharo. > at the same time, this is because we are still not signing Pharo, then apple moves it to a sandbox, which is bad. I have in my TODO signing the apps, but still no time to do it :/ > > Esteban > >> >> -Todd Blanchard >> >>> On Oct 30, 2017, at 12:27 PM, ÐÐ¸ÐºÐµÐ½ÑÐ¸Ð¹ ÐÐ¾ÑÐ°Ð¿Ð¾Ð² <vikenti.potapov(a)gmail.com> wrote: >>> >>> >>> I've just downloaded Pharo 6.1 from pharo.org, unzipped it and started. And i've got an error: >>> "UTF8InvalidText: Invalid utf8 input detected" >>> >>> Whether i save image or not, every time i start it i get the same error. >>> >>> System: win 7 professional x64 on 6-core Athlon Phenom. >>> Locale: russian (cyrillic). >>> >>> Can i fix it by myself or i should forget about 6.1 until global bugfix? >>> >>> Vikenti Potapov >>> >> >> > >

Oct. 31, 2017

Re: [Pharo-users] What is code 137 / how to gracefully shut down via SIGTERM?

by Bruce O'Neel

Hi, Well, not so scary. Â That's the mac list. Â From a not so recent mac with Xcode 7 installed it looks like the below. The good news here is that the common signals have the same numbers. Â And how often do you get an SIGXCPU? cheers bruce #define SIGHUPÂ 1 Â Â Â /* hangup */ #define SIGINTÂ 2 Â Â Â /* interrupt */ #define SIGQUIT 3 Â Â Â /* quit */ #define SIGILLÂ 4 Â Â Â /* illegal instruction (not reset when caught) */ #define SIGTRAP 5 Â Â Â /* trace trap (not reset when caught) */ #define SIGABRT 6 Â Â Â /* abort() */ #define SIGPOLL 7 Â Â Â /* pollable event ([XSR] generated, not supported) */ #else Â /* (!_POSIX_C_SOURCE || _DARWIN_C_SOURCE) */ #define SIGIOTÂ SIGABRT /* compatibility */ #define SIGEMTÂ 7 Â Â Â /* EMT instruction */ #endifÂ /* (!_POSIX_C_SOURCE || _DARWIN_C_SOURCE) */ #define SIGFPEÂ 8 Â Â Â /* floating point exception */ #define SIGKILL 9 Â Â Â /* kill (cannot be caught or ignored) */ #define SIGBUSÂ 10Â Â Â /* bus error */ #define SIGSEGV 11Â Â Â /* segmentation violation */ #define SIGSYSÂ 12Â Â Â /* bad argument to system call */ #define SIGPIPE 13Â Â Â /* write on a pipe with no one to read it */ #define SIGALRM 14Â Â Â /* alarm clock */ #define SIGTERM 15Â Â Â /* software termination signal from kill */ #define SIGURGÂ 16Â Â Â /* urgent condition on IO channel */ #define SIGSTOP 17Â Â Â /* sendable stop signal not from tty */ #define SIGTSTP 18Â Â Â /* stop signal from tty */ #define SIGCONT 19Â Â Â /* continue a stopped process */ #define SIGCHLD 20Â Â Â /* to parent on child stop or exit */ #define SIGTTIN 21Â Â Â /* to readers pgrp upon background tty read */ #ifÂ (!defined(_POSIX_C_SOURCE) || defined(_DARWIN_C_SOURCE)) #define SIGIO Â 23Â Â Â /* input/output possible signal */ #endif #define SIGXCPU 24Â Â Â /* exceeded CPU time limit */ #define SIGXFSZ 25Â Â Â /* exceeded file size limit */ #define SIGVTALRM 26Â Â /* virtual time alarm */ #define SIGPROF 27Â Â Â /* profiling time alarm */ #ifÂ (!defined(_POSIX_C_SOURCE) || defined(_DARWIN_C_SOURCE)) #define SIGWINCH 28 Â Â /* window size changes */ #define SIGINFO 29Â Â Â /* information request */ #endif #define SIGUSR1 30Â Â Â /* user defined signal 1 */ #define SIGUSR2 31Â Â Â /* user defined signal 2 */ > Bruce O'Neel wrote: > > Hi, > > > > Posix requires that if the process is killed the return status is > > greater than 128. > > > > What is convention on linux systems is that if the process is sent a > > signal then the signal number is added to 128. Therefore 137 is SIGKILL > > (kill -9). SIGTERM is 143, SIGABRT is 134, SIGSEGV is 139, and so on. > > I've not seen an exception to this but there could be. > > > > Signals off of my closest linux system look like: > > > > #define SIGHUP 1 > > #define SIGINT 2 > > #define SIGQUIT 3 > > #define SIGILL 4 > > #define SIGTRAP 5 > > #define SIGABRT 6 > > #define SIGIOT 6 > > #define SIGBUS 7 > > #define SIGFPE 8 > > #define SIGKILL 9 > > #define SIGUSR1 10 > > #define SIGSEGV 11 > > #define SIGUSR2 12 > > #define SIGPIPE 13 > > #define SIGALRM 14 > > #define SIGTERM 15 > > Scary, because Esteban's sigtrapping package has them defined a bit > differently: > > { #category : #'class initialization' } > POSIXSignal class >> initialize [ > SIGHUP := 1. > SIGINT := 2. > SIGQUIT := 3. > SIGILL := 4. > SIGTRAP := 5. > SIGABRT := 6. > SIGPOLL := 7. > SIGIOT := SIGABRT. > SIGEMT := 7. > SIGFPE := 8. > SIGKILL := 9. > SIGBUS := 10. > SIGSEGV := 11. > SIGSYS := 12. > SIGPIPE := 13. > SIGALRM := 14. > SIGTERM := 15. > SIGURG := 16. > SIGSTOP := 17. > SIGTSTP := 18. > SIGCONT := 19. > SIGCHLD := 20. > SIGTTIN := 21. > SIGTTOU := 22. > SIGIO := 23. > SIGXCPU := 24. > SIGXFSZ := 25. > SIGVTALRM := 26. > SIGPROF := 27. > SIGWINCH := 28. > SIGINFO := 29. > SIGUSR1 := 30. > SIGUSR2 := 31. > ]

Oct. 31, 2017

Re: [Pharo-users] Pharo 6.1

by Todd Blanchard

Actually, it is in Applications Sent from the road > On Oct 31, 2017, at 02:34, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > > >> On 30 Oct 2017, at 20:30, Todd Blanchard <tblanchard(a)mac.com> wrote: >> >> I was just preparing a similar post. Just downloaded latest Pharo 6.1-64 for Mac >> >> I was greeted with a walkback when it failed to create directory /private/var/folders/ks/wg6l98bj64q6hgvs23wwqypr0000gn/T/AppTranslocation/DAA5EA3A-374D-4ADE-9E04-BBB7433BB6C8/d/Pharo6.1-64.app/Contents/Resources/pharo-local >> >> Definitely not the right directory to resolve pharo-local to. > > not related :) > this is because you didnât put Pharo under /Applications as indicated when you download Pharo. > at the same time, this is because we are still not signing Pharo, then apple moves it to a sandbox, which is bad. I have in my TODO signing the apps, but still no time to do it :/ > > Esteban > >> >> -Todd Blanchard >> >>> On Oct 30, 2017, at 12:27 PM, ÐÐ¸ÐºÐµÐ½ÑÐ¸Ð¹ ÐÐ¾ÑÐ°Ð¿Ð¾Ð² <vikenti.potapov(a)gmail.com> wrote: >>> >>> >>> I've just downloaded Pharo 6.1 from pharo.org, unzipped it and started. And i've got an error: >>> "UTF8InvalidText: Invalid utf8 input detected" >>> >>> Whether i save image or not, every time i start it i get the same error. >>> >>> System: win 7 professional x64 on 6-core Athlon Phenom. >>> Locale: russian (cyrillic). >>> >>> Can i fix it by myself or i should forget about 6.1 until global bugfix? >>> >>> Vikenti Potapov >>> >> >> > >

Oct. 31, 2017

Re: [Pharo-users] What is code 137 / how to gracefully shut down via SIGTERM?

by Herby VojÄÃk

Bruce O'Neel wrote: > Hi, > > Posix requires that if the process is killed the return status is > greater than 128. > > What is convention on linux systems is that if the process is sent a > signal then the signal number is added to 128. Therefore 137 is SIGKILL > (kill -9). SIGTERM is 143, SIGABRT is 134, SIGSEGV is 139, and so on. > I've not seen an exception to this but there could be. > > Signals off of my closest linux system look like: > > #define SIGHUP 1 > #define SIGINT 2 > #define SIGQUIT 3 > #define SIGILL 4 > #define SIGTRAP 5 > #define SIGABRT 6 > #define SIGIOT 6 > #define SIGBUS 7 > #define SIGFPE 8 > #define SIGKILL 9 > #define SIGUSR1 10 > #define SIGSEGV 11 > #define SIGUSR2 12 > #define SIGPIPE 13 > #define SIGALRM 14 > #define SIGTERM 15 Scary, because Esteban's sigtrapping package has them defined a bit differently: { #category : #'class initialization' } POSIXSignal class >> initialize [ SIGHUP := 1. SIGINT := 2. SIGQUIT := 3. SIGILL := 4. SIGTRAP := 5. SIGABRT := 6. SIGPOLL := 7. SIGIOT := SIGABRT. SIGEMT := 7. SIGFPE := 8. SIGKILL := 9. SIGBUS := 10. SIGSEGV := 11. SIGSYS := 12. SIGPIPE := 13. SIGALRM := 14. SIGTERM := 15. SIGURG := 16. SIGSTOP := 17. SIGTSTP := 18. SIGCONT := 19. SIGCHLD := 20. SIGTTIN := 21. SIGTTOU := 22. SIGIO := 23. SIGXCPU := 24. SIGXFSZ := 25. SIGVTALRM := 26. SIGPROF := 27. SIGWINCH := 28. SIGINFO := 29. SIGUSR1 := 30. SIGUSR2 := 31. ]

Oct. 31, 2017

Re: [Pharo-users] What is code 137 / how to gracefully shut down via SIGTERM?

by Bruce O'Neel

Hi, Posix requires that if the process is killed the return status is greater than 128. What is convention on linux systems is that if the process is sent a signal then the signal number is added to 128. Â Therefore 137 is SIGKILL (kill -9). Â SIGTERM is 143, SIGABRT is 134, SIGSEGV is 139, and so on. Â I've not seen an exception to this but there could be. Signals off of my closest linux system look like: #define SIGHUP Â Â Â Â Â 1 #define SIGINT Â Â Â Â Â 2 #define SIGQUITÂ Â Â Â Â 3 #define SIGILL Â Â Â Â Â 4 #define SIGTRAPÂ Â Â Â Â 5 #define SIGABRTÂ Â Â Â Â 6 #define SIGIOT Â Â Â Â Â 6 #define SIGBUS Â Â Â Â Â 7 #define SIGFPE Â Â Â Â Â 8 #define SIGKILLÂ Â Â Â Â 9 #define SIGUSR1 Â Â Â Â 10 #define SIGSEGV Â Â Â Â 11 #define SIGUSR2 Â Â Â Â 12 #define SIGPIPE Â Â Â Â 13 #define SIGALRM Â Â Â Â 14 #define SIGTERM Â Â Â Â 15 SIGHUP is the phone hung up. Â SIGINT is interrupt (^C) SIGILL is you tried to execute an illegal instruction, SIGBUS is Bus error, normally you tried to read a 32 bit value on a non-32 bit boundary and uncommon on x86, SIGFPE is a floating point error, SIGKILL is too bad, you're dead, SIGSEGV is you tried to read/write memory that was not allowed, and SIGTERM is the normal "please exit" signal. cheers bruce > werner kassens wrote: > > Hi Herby, > > eventually you might want to look at > > https://github.com/moby/moby/issues/1063 > > but then i dont know anything about these things. > > Hopefully they have this solved already... but I learned 137 means > "killed". generally; did not know. :-) > > > werner > > Herby Hi,

Oct. 31, 2017

Re: [Pharo-users] Smalltalk Argument

by Hans

Hi all, an argument for Smalltalk, an discussion coming up many times in my history. It is also something I'm asking myself from time to time. It is very actual in the moment. Many good arguments were mentioned this discussion. I want to provide you my 2 cents on this. First, I'm taking the view of an hobby enthusiast. That's were I started. All the time I was excited by the Smalltalk concept. Live debugging, VM system, the possibility to look at and understand every code from systems completely new to me was so great. No installation, and nice people in the community. Conclusion: I want to do all in Smalltalk. Elegance is what rules only. Now, I'm in the perspective of an employed software developer. Everywhere that crazy C++, sometimes Fortran or C. Delphi. The people told "that's old, that was the beginning years ago, that is given, we have nothing else". And we have no time to redesign or port to something better, so fate catched us and we have to continue on the road to hell..... Most of my life colleagues were physicists who learned C++ for its thesis, or engineers of the embedded domain. No or only a few computer scientists. The rule now on these days: get ready, it should work somehow, costs. Elegance or sound design is no value. Not at this time. SW is just a part of my component as any screw and nail too. Continuing as a team leader. My goal is to fit budget. I have some time, and I have some people in the team. And I have to report and sell to my manager above me. I'm looking for get the job done, but I have also some strategic view. I've read some articles about this new .Net, with big potential, many libraries. Easy Web. Web is the future. I ask my team how to solve the task. Ony guy talks about Pearl. I hat Pearl. Another colleagues tells something about Smalltalk. Never heared of it, I ask if this is compatible to .Net.... My rules of success are in what I belief - and what can I sell to my big boss. And I belief only what I see... I could continue this. My point is: the Smalltalk Argument is depending on the perspective. And therefore, to communicate and argue about Smalltalk is what the receiver of the argument needs. Superiour technique can be an argument, but not always. Missing developer can be an argument, but not in every company and every project. My personal conclusion and look to Smalltalk is this: - for my soul which want to bring science and technology to the future, I look at the elegance and power of Smalltalk. That's why I'm looking at TeaTime and OpenCroquet again in the age of AR. - if I want to learn from top coders, the way of developing in Smalltalk (live debugging) - if I want to get a job done (for example a web site), I'm looking what the world offers me. And it may not be Smalltalk. In my current work, Game Engines matter. So coding a Game Engine in Smalltalk ? May be, but there are a lot of good products already... Having said that, the Smalltalk Argument has to sides, and they have both their value: - Smalltalk as an technique, as a matter of research and getting things better, an philosophy - Smalltalk as a product for people who want things get done. My personal opinion is that sometimes the point Smalltalk (or better now: Pharo) as a product is not so much in concern as it could. Pharo evolved wonderfully, the consortium and the organisation and the community have the right direction, yes. But as an industrial user of software I only can hope: keep the Smalltalk as a Product in the same focus as Smalltalk as the better technology. And product means: look at the needs the product is indented for, look at the "market". What are the problems out there ? If you can fit the needs, and provide a productive and integrable technology, you need no argument for Smalltalk. Off topic: thanks for the big effort of the community, it is really really fun today to work on and with Pharo. Much happend, and much is possible ;) Cheers Hans -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Oct. 31, 2017

Re: [Pharo-users] Smalltalk Argument

by Hans

Hi all, an argument for Smalltalk, an discussion coming up many times in my history. It is also something I'm asking myself from time to time. It is very actual in the moment. Many good arguments were mentioned this discussion. I want to provide you my 2 cents on this. First, I'm taking the view of an hobby enthusiast. That's were I started. All the time I was excited by the Smalltalk concept. Live debugging, VM system, the possibility to look at and understand every code from systems completely new to me was so great. No installation, and nice people in the community. Conclusion: I want to do all in Smalltalk. Elegance is what rules only. Now, I'm in the perspective of an employed software developer. Everywhere that crazy C++, sometimes Fortran or C. Delphi. The people told "that's old, that was the beginning years ago, that is given, we have nothing else". And we have no time to redesign or port to something better, so fate catched us and we have to continue on the road to hell..... Most of my life colleagues were physicists who learned C++ for its thesis, or engineers of the embedded domain. No or only a few computer scientists. The rule now on these days: get ready, it should work somehow, costs. Elegance or sound design is no value. Not at this time. SW is just a part of my component as any screw and nail too. Continuing as a team leader. My goal is to fit budget. I have some time, and I have some people in the team. And I have to report and sell to my manager above me. I'm looking for get the job done, but I have also some strategic view. I've read some articles about this new .Net, with big potential, many libraries. Easy Web. Web is the future. I ask my team how to solve the task. Ony guy talks about Pearl. I hat Pearl. Another colleagues tells something about Smalltalk. Never heared of it, I ask if this is compatible to .Net.... My rules of success are in what I belief - and what can I sell to my big boss. And I belief only what I see... I could continue this. My point is: the Smalltalk Argument is depending on the perspective. And therefore, to communicate and argue about Smalltalk is what the receiver of the argument needs. Superiour technique can be an argument, but not always. Missing developer can be an argument, but not in every company and every project. My personal conclusion and look to Smalltalk is this: - for my soul which want to bring science and technology to the future, I look at the elegance and power of Smalltalk. That's why I'm looking at TeaTime and OpenCroquet again in the age of AR. - if I want to learn from top coders, the way of developing in Smalltalk (live debugging) - if I want to get a job done (for example a web site), I'm looking what the world offers me. And it may not be Smalltalk. In my current work, Game Engines matter. So coding a Game Engine in Smalltalk ? May be, but there are a lot of good products already... Having said that, the Smalltalk Argument has to sides, and they have both their value: - Smalltalk as an technique, as a matter of research and getting things better, an philosophy - Smalltalk as a product for people who want things get done. My personal opinion is that sometimes the point Smalltalk (or better now: Pharo) as a product is not so much in concern as it could. Pharo evolved wonderfully, the consortium and the organisation and the community have the right direction, yes. But as an industrial user of software I only can hope: keep the Smalltalk as a Product in the same focus as Smalltalk as the better technology. And product means: look at the needs the product is indented for, look at the "market". What are the problems out there ? If you can fit the needs, and provide a productive and integrable technology, you need no argument for Smalltalk. Off topic: thanks for the big effort of the community, it is really really fun today to work on and with Pharo. Much happend, and much is possible ;) Cheers Hans -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Oct. 31, 2017

Re: [Pharo-users] Pharo 6.1

by Esteban Lorenzano

> On 30 Oct 2017, at 20:30, Todd Blanchard <tblanchard(a)mac.com> wrote: > > I was just preparing a similar post. Just downloaded latest Pharo 6.1-64 for Mac > > I was greeted with a walkback when it failed to create directory /private/var/folders/ks/wg6l98bj64q6hgvs23wwqypr0000gn/T/AppTranslocation/DAA5EA3A-374D-4ADE-9E04-BBB7433BB6C8/d/Pharo6.1-64.app/Contents/Resources/pharo-local > > Definitely not the right directory to resolve pharo-local to. not related :) this is because you didnât put Pharo under /Applications as indicated when you download Pharo. at the same time, this is because we are still not signing Pharo, then apple moves it to a sandbox, which is bad. I have in my TODO signing the apps, but still no time to do it :/ Esteban > > -Todd Blanchard > >> On Oct 30, 2017, at 12:27 PM, ÐÐ¸ÐºÐµÐ½ÑÐ¸Ð¹ ÐÐ¾ÑÐ°Ð¿Ð¾Ð² <vikenti.potapov(a)gmail.com> wrote: >> >> >> I've just downloaded Pharo 6.1 from pharo.org, unzipped it and started. And i've got an error: >> "UTF8InvalidText: Invalid utf8 input detected" >> >> Whether i save image or not, every time i start it i get the same error. >> >> System: win 7 professional x64 on 6-core Athlon Phenom. >> Locale: russian (cyrillic). >> >> Can i fix it by myself or i should forget about 6.1 until global bugfix? >> >> Vikenti Potapov >> > >

Oct. 31, 2017

Re: [Pharo-users] QCMagritte on Github

by laurent

Hi Diego, we used this process to migrate: https://github.com/peteruhnak/git-migration. So we have all history of QCMagritte (including ConfigurationOf). We created the BaselineOf but it only loads latest packages (see https://github.com/Afibre/QCMagritte/blob/master/src/BaselineOfQCMagritte.p… ). So there should be made branches for the different Pharo versions. If you give me your github I can give you write access to the github repository. Laurent Le dim. 29 oct. 2017 Ã 13:42, Diego Lont <diego.lont(a)delware.nl> a Ã©crit : > Hi, > > It was somewhere on my todo list to migrate to Github, but not very > highâ¦ > > but I guess if someone else does this for me, I should be happy about > this. > > So thank you, I will look up my gut hub account and also change the > job. I hope to do this somewhere next week. > > I know there a different configurations for different versions of > pharo, so did you import only one version, or should there be made > branches for the different pharo version? > > Regards, > Diego > >> On 27 Oct 2017, at 16:50, laurent laffont >> <laurent.laffont(a)gmail.com> wrote: >> >> I've added loading instructions in README: >> >> Metacello new >> githubUser: 'Afibre' project: 'QCMagritte' commitish: 'master' >> path: 'src'; >> baseline: 'QCMagritte'; >> load. >> >> >> For the QCMagritte version, there's actually one branch master. If >> you >> need a previous version, I suppose the right way is to create a >> github >> branch from the desired commit in git history and adapt the >> BaselineOf... >> >> Laurent >> >> On Fri, Oct 27, 2017 at 2:12 PM, HernÃ¡n Morales Durand >> <hernan.morales(a)gmail.com> wrote: >>> Nice to know Laurent, >>> >>> Could you please comment or share how to install this version >>> uploaded >>> to GitHub? >>> Any way to check the installed or current QCMagritte version? >>> >>> Cheers, >>> >>> HernÃ¡n >>> >>> >>> >>> >>> 2017-10-27 7:39 GMT-03:00 laurent laffont >>> <laurent.laffont(a)gmail.com>: >>>> Hi, >>>> >>>> my team starts to use QCMagritte. For our needs we have imported >>>> SmalltalkHub repository to Github here: >>>> https://github.com/Afibre/QCMagritte >>>> >>>> I don't know if you (Diego, Stephan, Tobias) plan to use Github >>>> instead of SmalltalkHub. At least Github allows branches & pull >>>> request. >>>> >>>> Regards, >>>> >>>> Laurent Laffont >>>> >>> >> > >

Oct. 31, 2017