December 2017 - Pharo-users

Re: [Pharo-users] Active IRC Chanel

by Esteban Lorenzano

> On 21 Dec 2017, at 08:27, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > > >> On 21 Dec 2017, at 04:34, Ian Ian <icjohnsoia(a)gmail.com> wrote: >> >> Hi All, >> >> Is there an active IRC Chanel? > > No. There is (or was) an inactive one. > > >> Read somewhere (can't remember) that there is one labeled #pharo. Is this true if so may I ask on which server it resides? >> > > > I guess it is still there, it was on freenode I think. > > The Discord chat is quite active. For me it works much better than IRC. Maybe I had just a bad IRC > client, but it never was a nice experience. yes. I donât understand why, but #irc channel never worked while discord works pretty well and is very active. I meanâ¦ at the end, discord is no more than a glorified irc, but wellâ¦ one works and the other donât :) Esteban > > Marcus

Dec. 21, 2017

Re: [Pharo-users] Iceberg, Git and Package version

by Vitor Medina Cruz

Then in a Metacello configuration should I reference the hash git commit or a tag in a version method? For example, an extract from Deep in Pharo: ConfigurationOfCoolToolSet>>version02: spec > <version: '0.2' imports: #('0.2-baseline' )> > spec for: #common do: [ > spec blessing: #beta. > spec > package: 'CoolToolSet-Core' with: 'CoolToolSet-Core-AlanJay.1'; > package: 'CoolToolSet-Tests' with: 'CoolToolSet-Tests-AlanJay.1'; > project: 'CoolBrowser default' with: '1.3'; > project: 'CoolBrowser Tests' with: '1.3']. > In this case 'CoolToolSet-Core-AlanJay.1' would be changed by 'CoolToolSet-Core-<git_hash>'? On Wed, Dec 20, 2017 at 6:09 PM, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > In iceberg you can specify > - latest version when you do not specify anything > - a version (but it should be a git tag so you should save you code > with a tag - iceberg does not support it right now but you can do it > with git) > - the hash of your git commit. > > Does it answer your question? > Stef > > > On Wed, Dec 20, 2017 at 7:51 PM, Vitor Medina Cruz <vitormcruz(a)gmail.com> > wrote: > > Hello, > > > > How are packages versions computed in Iceberg? > > > > I am looking at the Metacello documentation at 'Deep in Pharo', it says I > > can define dependencies at package level and it uses the following > format to > > identify versions: <dev_name.versionNumber>; which I think is a pattern > used > > by Monticello, right? However, I can't figure what is the equivalent (if > > any) in Iceberg. > > > > Thanks in Advance, > > Vitor > >

Dec. 21, 2017

Re: [Pharo-users] Athens error

by Hilaire

Hi Ben, * The Linux 64 bits VM is the one coming from P6/P6.1, it is the only way to get one. * To install the project, fetch the src code from the DrGeo repo: bzr branch lp:drgeo * In the trunk/build/image directory install a virgin P7 image * You have to symlink /images/src to trunk/src * Adjust trunk/build/make-workstation-release script: Â Â Â smalltalkImage and src variable. These make-workstation-script will be refactored some days with appropriate shell function. Le 20/12/2017 Ã 23:28, Ben Coman a Ã©critÂ : > Hi Hilaire, > > I'll have a try at reproducing your issue.Â Could you provide a > download link to the VM you are using, > and instructions how to load your project and trigger the problem. > > cheers -ben -- Dr. Geo http://drgeo.eu

Dec. 21, 2017

Re: [Pharo-users] [ANN] Pharo Consortium New Bronze Member: Object Profile

by Marcus Denker

I added this to the Pharo news page (http://pharo.org/news <http://pharo.org/news>): [ANN] Pharo Consortium New Bronze Member: Object Profile http://pharo.org/news/consortium-object-profile <http://pharo.org/news/consortium-object-profile> > On 21 Dec 2017, at 08:41, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > The Pharo Consortium is very happy to announce that Object Profile > has joined the Consortium as a Bronze Member. > > About > - Object Profile: http://objectprofile.com > - Pharo Consortium: http://consortium.pharo.org > > The goal of the Pharo Consortium is to allow companies and institutions to > support the ongoing development and future of Pharo. > > Individuals can support Pharo via the Pharo Association: > > - http://association.pharo.org

Dec. 21, 2017

[ANN] Pharo Consortium New Bronze Member: Object Profile

by Marcus Denker

The Pharo Consortium is very happy to announce that Object Profile has joined the Consortium as a Bronze Member. About - Object Profile: http://objectprofile.com - Pharo Consortium: http://consortium.pharo.org The goal of the Pharo Consortium is to allow companies and institutions to support the ongoing development and future of Pharo. Individuals can support Pharo via the Pharo Association: - http://association.pharo.org

Dec. 21, 2017

Re: [Pharo-users] Active IRC Chanel

by Marcus Denker

> On 21 Dec 2017, at 04:34, Ian Ian <icjohnsoia(a)gmail.com> wrote: > > Hi All, > > Is there an active IRC Chanel? No. There is (or was) an inactive one. > Read somewhere (can't remember) that there is one labeled #pharo. Is this true if so may I ask on which server it resides? > I guess it is still there, it was on freenode I think. The Discord chat is quite active. For me it works much better than IRC. Maybe I had just a bad IRC client, but it never was a nice experience. Marcus

Dec. 21, 2017

Re: [Pharo-users] Metacello with Git

by Norbert Hartl

> Am 21.12.2017 um 03:27 schrieb Sean P. DeNigris <sean(a)clipperadams.com>: > > Tudor Girba-2 wrote >> We also use private GitHub projects with Iceberg and it works fine. >>> Au contraire! It works really good with SSH keys. I work all day with it. >>> I added support for bitbucket to iceberg because Iâm using bitbucket >>> private repos in my company. > > This is very intriguing. So you're saying one can now use GH and BB URLs to > access private repos in baselines for dependent projects and they will be > loaded via SSH keys? > Yes, I have projects that are loaded from bitbucket private repos and that have dependencies to public github and private bitbucket repos all at once. Not a problem on my dev machine. On jenkins it is more of a problem. There the ssh keys are provided by the jenkins server but if a dependent project is also private there needs to be ssh keys in the environment. Second thing is that the linux 64bit vm is pretty unstable. This could be avoided using filetree and zip downloads from git but there is no way providing credentials to the https download. Either way not good. I even made one project public in order to load it Norbert > > > ----- > Cheers, > Sean > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Dec. 21, 2017

Active IRC Chanel

by Ian Ian

Hi All, Is there an active IRC Chanel? Read somewhere (can't remember) that there is one labeled #pharo. Is this true if so may I ask on which server it resides? Kindly in advance,

Dec. 21, 2017

Re: [Pharo-users] Metacello with Git

by Sean P. DeNigris

Tudor Girba-2 wrote > We also use private GitHub projects with Iceberg and it works fine. >> Au contraire! It works really good with SSH keys. I work all day with it. >> I added support for bitbucket to iceberg because Iâm using bitbucket >> private repos in my company. This is very intriguing. So you're saying one can now use GH and BB URLs to access private repos in baselines for dependent projects and they will be loaded via SSH keys? ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Dec. 21, 2017

Re: [Pharo-users] Athens error

by Ben Coman

On 17 December 2017 at 05:29, Hilaire <hilaire(a)drgeo.eu> wrote: > Hi, > > With DrGeo built on image Pharo7.0-64bit-e41f921 Athens error shows up on > the canvas (screenshot). > > The drgeo dev. environment based on the older Pharo7.0-64bit-f82fc36 image > does not have this error with the same VM. > > The DrGeo build removes some pharo package but it is unlikely to produce > such error, or so? > > -- > Dr. Geo > http://drgeo.eu > > Hi Hilaire, I'll have a try at reproducing your issue. Could you provide a download link to the VM you are using, and instructions how to load your project and trigger the problem. cheers -ben

Dec. 20, 2017