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
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@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
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@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@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
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@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@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@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
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.pa... ). 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@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@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@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@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
On 27-10-17 12:39, laurent laffont wrote:
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.
Definitely, and I'm still struggling a bit with Iceberg. I would definitely favor a setup where the whole open source part is build on each commit using travis and images are put on (e.g.) bitbucket. The current jenkins builds are waiting for Diego to finish some changes, and he is a bit distracted with plans for a new house. Tobias told me he's also interested, so I assume he'll provide a modified baseline for other platforms. At a certain point we might want to fold all of QCMagritte back into Magritte, but that is a discussion for later I think. Stephan
On 08.11.2017, at 08:15, stephan <stephan@stack.nl> wrote:
Tobias told me he's also interested, so I assume he'll provide a modified baseline for other platforms.
Modulo time, as always. If the convex hull of the dependencies need too much changes for other platforms, I might have to drop that endeavor :/ -t
On 08-11-17 20:53, Tobias Pape wrote:
Modulo time, as always. If the convex hull of the dependencies need too much changes for other platforms, I might have to drop that endeavor :/
And I trust you'll complain about our lack of responsible dependency management in that case Stephan
Hi, Le mer. 8 nov. 2017 à 8:15, stephan <stephan@stack.nl> a écrit :
Definitely, and I'm still struggling a bit with Iceberg. I would definitely favor a setup where the whole open source part is build on each commit using travis and images are put on (e.g.) bitbucket.
Now a QCMagritte image (vm 64) is built by Travis on each commit, see https://github.com/Afibre/QCMagritte/releases and https://travis-ci.org/Afibre/QCMagritte Laurent
On 10-11-17 15:59, laurent wrote:
Now a QCMagritte image (vm 64) is built by Travis on each commit, see
https://github.com/Afibre/QCMagritte/releases
and
Thanks, Laurent, good to see progress being made. Stephan
Stephan Eggermont-3 wrote
At a certain point we might want to fold all of QCMagritte back into Magritte, but that is a discussion for later I think.
If you get around to that, also feel free to steal anything you might find interesting from https://github.com/seandenigris/Magritte3 where I've been actively developing. I forked because I was developing on the fly for myself and I was worried about cross platform compatibility (I always use stable Pharo) and sometimes breaking CI. At this point there are a few hundred commits from simple cleanups to brand new features. ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html
For your information. We got some problem with travis (what a bad idea to have a syntax like yaml - our industry is looping , even xml is better). we spent more than 30 min trying with Guille and Andrew to use bash in a script section (while this is working in some guille project) it does not in other just because yaml does not know who to find the end of a line.... Terrible! Stef On Wed, Nov 8, 2017 at 8:15 AM, stephan <stephan@stack.nl> wrote:
On 27-10-17 12:39, laurent laffont wrote:
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.
Definitely, and I'm still struggling a bit with Iceberg. I would definitely favor a setup where the whole open source part is build on each commit using travis and images are put on (e.g.) bitbucket. The current jenkins builds are waiting for Diego to finish some changes, and he is a bit distracted with plans for a new house.
Tobias told me he's also interested, so I assume he'll provide a modified baseline for other platforms.
At a certain point we might want to fold all of QCMagritte back into Magritte, but that is a discussion for later I think.
Stephan
YAML is what it says, lol. I still prefer using SGML and outputting whatever markup I need, although I have to use US army software (that only works on Windows) to do it since Adobe gouges for FrameMaker. Probably a long lasting hangover from working for IBM years ago. Sure was a headache, so a hangover isnât that surprising. Looking for the latest version of that software for a new Win 10 install I came across one of the best quotes on Windows, especially considering the source, though the quote mustâve been written about an old version. âWith luck, this will start Windows, and a dialogue box will appear and tell you the default drive into which IADS will be installed (C:). If Windows doesn't start up, you could always try launching Windows manually.â Andrew From: Stephane Ducasse Sent: Friday, November 10, 2017 1:21 PM To: Any question about pharo is welcome Subject: Re: [Pharo-users] QCMagritte on Github For your information. We got some problem with travis (what a bad idea to have a syntax like yaml - our industry is looping , even xml is better). we spent more than 30 min trying with Guille and Andrew to use bash in a script section (while this is working in some guille project) it does not in other just because yaml does not know who to find the end of a line.... Terrible! Stef On Wed, Nov 8, 2017 at 8:15 AM, stephan <stephan@stack.nl> wrote:
On 27-10-17 12:39, laurent laffont wrote:
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.
Definitely, and I'm still struggling a bit with Iceberg. I would definitely favor a setup where the whole open source part is build on each commit using travis and images are put on (e.g.) bitbucket. The current jenkins builds are waiting for Diego to finish some changes, and he is a bit distracted with plans for a new house.
Tobias told me he's also interested, so I assume he'll provide a modified baseline for other platforms.
At a certain point we might want to fold all of QCMagritte back into Magritte, but that is a discussion for later I think.
Stephan
Found this on /r/programming today. Seemed relevant. Gist is that YAML spec is ambiguous and implementations seem to disagree widely on proper interpretation. https://github.com/cblp/yaml-sucks
On Nov 10, 2017, at 10:37 AM, Andrew Glynn <aglynn42@gmail.com> wrote:
YAML is what it says, lol.
I still prefer using SGML and outputting whatever markup I need, although I have to use US army software (that only works on Windows) to do it since Adobe gouges for FrameMaker.
Probably a long lasting hangover from working for IBM years ago. Sure was a headache, so a hangover isnât that surprising.
Looking for the latest version of that software for a new Win 10 install I came across one of the best quotes on Windows, especially considering the source, though the quote mustâve been written about an old version.
âWith luck, this will start Windows, and a dialogue box will appear and tell you the default drive into which IADS will be installed (C:).
If Windows doesn't start up, you could always try launching Windows manually.â
Andrew
From: Stephane Ducasse <mailto:stepharo.self@gmail.com> Sent: Friday, November 10, 2017 1:21 PM To: Any question about pharo is welcome <mailto:pharo-users@lists.pharo.org> Subject: Re: [Pharo-users] QCMagritte on Github
For your information. We got some problem with travis (what a bad idea to have a syntax like yaml - our industry is looping , even xml is better). we spent more than 30 min trying with Guille and Andrew to use bash in a script section (while this is working in some guille project) it does not in other just because yaml does not know who to find the end of a line....
Terrible!
Stef
On Wed, Nov 8, 2017 at 8:15 AM, stephan <stephan@stack.nl> wrote:
On 27-10-17 12:39, laurent laffont wrote:
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.
Definitely, and I'm still struggling a bit with Iceberg. I would definitely favor a setup where the whole open source part is build on each commit using travis and images are put on (e.g.) bitbucket. The current jenkins builds are waiting for Diego to finish some changes, and he is a bit distracted with plans for a new house.
Tobias told me he's also interested, so I assume he'll provide a modified baseline for other platforms.
At a certain point we might want to fold all of QCMagritte back into Magritte, but that is a discussion for later I think.
Stephan
Iâll agree that YAML is not an ideal syntax - but I have to also add that I wasnât that impressed with Travis either, and reading between the lines its the combo of both that might be catching you out. Even with a few glitches, Iâve been impressed with GitLab although the team I worked with recently found that CircleCI was more to their liking. In both cases you have much more control about what is going on. It may be that you need something a bit more heavy duty - and it might be worth checking out some of the alternatives. Tim
On 10 Nov 2017, at 18:20, Stephane Ducasse <stepharo.self@gmail.com> wrote:
For your information. We got some problem with travis (what a bad idea to have a syntax like yaml - our industry is looping , even xml is better). we spent more than 30 min trying with Guille and Andrew to use bash in a script section (while this is working in some guille project) it does not in other just because yaml does not know who to find the end of a line....
Terrible!
Stef
On Wed, Nov 8, 2017 at 8:15 AM, stephan <stephan@stack.nl> wrote:
On 27-10-17 12:39, laurent laffont wrote:
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.
Definitely, and I'm still struggling a bit with Iceberg. I would definitely favor a setup where the whole open source part is build on each commit using travis and images are put on (e.g.) bitbucket. The current jenkins builds are waiting for Diego to finish some changes, and he is a bit distracted with plans for a new house.
Tobias told me he's also interested, so I assume he'll provide a modified baseline for other platforms.
At a certain point we might want to fold all of QCMagritte back into Magritte, but that is a discussion for later I think.
Stephan
participants (11)
-
Andrew Glynn -
Diego Lont -
Hernán Morales Durand -
laurent -
laurent laffont
-
Sean P. DeNigris -
stephan -
Stephane Ducasse -
Tim Mackinnon -
Tobias Pape -
Todd Blanchard