[Pharo-users] [ANN] Gemtalk Systems upgraded to Gold Membership

[Marcus Denker]

The Pharo Consortium is very happy to announce that Gemtalk Systems
has upgraded to Gold Member status.

About
- Gemtalk Systems: https://gemtalksystems.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

Re: [Pharo-users] How to connect to DB2

[Stephane Ducasse]

Hi andrei

First welcome to this list.
Second can you explain to us what is the experience that you did so
that you can state that ODBC is broken in Pharo 6.1?

Stef

On Thu, Dec 21, 2017 at 11:48 PM, Andrei Stebakov  wrote:
> Looks like ODBC is broken in Pharo 6.1.
> What's the best way to get access to DB2 in Pharo?
>
>

Re: [Pharo-users] And Mac too Re: [ANN] OpenSSL-Pharo works on Windows

[Stephane Ducasse]

We appreciate it!


On Fri, Dec 22, 2017 at 3:38 AM, Pierce Ng  wrote:
> On Wed, Dec 20, 2017 at 08:57:59PM +0100, Stephane Ducasse wrote:
>> great news.
>> And this is super great that you plan to work on different platforms!
>> THANKS
>
> This is my little way of giving back to Pharo and the community.
>
> And now I have added #macModuleName to the library and tested it successfully
> with 64-bit Pharo on my Mac that runs Sierra.
>
> Pierce
>
>

Re: [Pharo-users] HMAC-SHA512

[Pierce Ng]

On Tue, Dec 12, 2017 at 12:52:11AM +0800, Ben Coman wrote:
> I was going to ask why these updates aren't being pushed an OpenSSL repo
> shared with Squeak,
> since things should not be much different at this low level, but actually
> it was hard to
> determine which was the original repo. I see...
>http://www.squeaksource.com/SqueakSSL.html
> seems to have not beenupdated since 2012.

I think this might be the SSL plugin which is now part of the VM and is still
called SqueakSSL.

My library is for access to the crypto/X509 functions in OpenSSL's libcrypto.

For green field applications I recommend using NaCl aka libsodium with its
modern algorithms and crypto-safe programming practices.

Pierce

[Pharo-users] And Mac too Re: [ANN] OpenSSL-Pharo works on Windows

[Pierce Ng]

On Wed, Dec 20, 2017 at 08:57:59PM +0100, Stephane Ducasse wrote:
> great news.
> And this is super great that you plan to work on different platforms!
> THANKS

This is my little way of giving back to Pharo and the community.

And now I have added #macModuleName to the library and tested it successfully
with 64-bit Pharo on my Mac that runs Sierra.

Pierce

Re: [Pharo-users] Metacello with Git

[Pierce Ng]

On Wed, Dec 20, 2017 at 06:08:16PM +0100, Thierry Goubier wrote:
> >Iceberg does, with RSA keys. Iceberg didn't work for me with ED25519 keys.
> does command line git work with those ED25519 keys?

Yes. I have been using GH with ED25519 keys.

I added RSA keys to my GH setup specifically for Iceberg. I looked and found
out that libssh2 or libgit2 (forgot which) used by Iceberg does not support
ED25519 keys.

Pierce

[Pharo-users] How to connect to DB2

[Andrei Stebakov]

Looks like ODBC is broken in Pharo 6.1.
What's the best way to get access to DB2 in Pharo?

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

[Stephane Ducasse]

Tx ObjectProfile

On Thu, Dec 21, 2017 at 8:41 AM, Marcus Denker  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
>

Re: [Pharo-users] Irc

[Ian Ian]

Thanks Estoban.  I'll check out discord.  :)

BTW, I am new to smalltalk. New to Pharo.  Liking both!  :)

On Dec 21, 2017 8:45 AM,  wrote:

Send Pharo-users mailing list submissions to
pharo-users@lists.pharo.org

To subscribe or unsubscribe via the World Wide Web, visit
http://lists.pharo.org/mailman/listinfo/pharo-users_lists.pharo.org
or, via email, send a message with subject or body 'help' to
pharo-users-requ...@lists.pharo.org

You can reach the person managing the list at
pharo-users-ow...@lists.pharo.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Pharo-users digest..."

Today's Topics:

   1. Re: Active IRC Chanel (Esteban Lorenzano)
   2. Re: Iceberg, Git and Package version (Esteban Lorenzano)
   3. Re: Iceberg, Git and Package version (Esteban Lorenzano)
   4. Hi, do I nowadays need any Id and psw, to log in smalltalk
  hub and others? (Janko Korelc)
   5. Re: Iceberg, Git and Package version (Vitor Medina Cruz)


-- Forwarded message --
From: Esteban Lorenzano 
To: Any question about pharo is welcome 
Cc:
Bcc:
Date: Thu, 21 Dec 2017 11:10:55 +0100
Subject: Re: [Pharo-users] Active IRC Chanel


> On 21 Dec 2017, at 08:27, Marcus Denker  wrote:
>
>
>
>> On 21 Dec 2017, at 04:34, Ian Ian  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





-- Forwarded message --
From: Esteban Lorenzano 
To: Any question about pharo is welcome 
Cc:
Bcc:
Date: Thu, 21 Dec 2017 11:22:59 +0100
Subject: Re: [Pharo-users] Iceberg, Git and Package version


On 20 Dec 2017, at 19:51, Vitor Medina Cruz  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: ; 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


Hi Vitor,

Package versions do not have any sense on iceberg, where what has sense is
the “project” version. All packages point to a commit in repo.

This is to say, you do not load single package in iceberg but you load a
repository version (which is the commit).
That’s why you use Metacello expressions like this:

Metacello new
repository: ‘github://someuser/someproject:sometag';
baseline: ‘Blah’;
load.

and in your baselines, when you include another project you do

spec
baseline: ‘Blah’
with: [ spec repository: ‘github://someuser/someproject:sometag' ].

cheers!
Esteban


-- Forwarded message --
From: Esteban Lorenzano 
To: Any question about pharo is welcome 
Cc:
Bcc:
Date: Thu, 21 Dec 2017 12:02:54 +0100
Subject: Re: [Pharo-users] Iceberg, Git and Package version


On 21 Dec 2017, at 11:03, Vitor Medina Cruz  wrote:

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
> 
> 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’].
>

the thing is: you don’t use configurations with iceberg projects, you use
baselines.

Esteban


In this case  'CoolToolSet-Core-AlanJay.1' would be changed by
'CoolToolSet-Core-'?

On Wed, Dec 20, 2017 at 6:09 PM, Stephane Ducasse 
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 
> wrote:
> > Hello,
> >
> > How are packages versions computed in Iceberg?
> >
> 

Re: [Pharo-users] Hi, do I nowadays need any Id and psw, to log in smalltalk hub and others?

[Stephane Ducasse]

Hi

To publish code you need to have an account on SmalltalkHub.
Else to access code you do not need.

Stef


On Thu, Dec 21, 2017 at 1:50 PM, Janko Korelc  wrote:
> ... as connection time out...
>
> Best Regards!
>
> Janko Korelc

Re: [Pharo-users] Active IRC Chanel

[Stephane Ducasse]

Hi ian


Welcome. Join the dicord channel  http://discord.gg/Sj2rhxn

Stef

On Thu, Dec 21, 2017 at 4:34 AM, Ian Ian  wrote:
> 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,

Re: [Pharo-users] Metacello with Git

[Norbert Hartl]

> Am 21.12.2017 um 15:54 schrieb Sean P. DeNigris :
> 
> NorbertHartl wrote
>> I have projects that are loaded from bitbucket private repos and that have
>> dependencies to… private bitbucket repos all at once.
> 
> Is `Iceberg enableMetacelloIntegration: true` what gets around the tarball /
> SSH-support issue?

Yes, metacello git integration will not download tarballs but checkout the git 
repo and therefor ssh can be used.

Norbert

Re: [Pharo-users] Metacello with Git

[Sean P. DeNigris]

NorbertHartl wrote
> I have projects that are loaded from bitbucket private repos and that have
> dependencies to… private bitbucket repos all at once.

Is `Iceberg enableMetacelloIntegration: true` what gets around the tarball /
SSH-support issue?



-
Cheers,
Sean
--
Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

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

[Vitor Medina Cruz]

>
> This is mostly true, but ATM you may want to wrap your BaselineOf in a
> ConfigurationOf (i.e. refer to A with a SHA from B) for tool integration
> e.g. only Configs show up in the catalog. IIUC, one additional constraint
> to
> be aware of (not sure how important it is in practice) is that in the past
> with mcz repos, one could refer to a specific version of each package, but
> now you would only be able to specify a version for the whole git repo.


I was about to ask that after reading through Metacello docs — While I find
usefull to define groups and dependencies at package level (I need only
package A from ThatProject on version 2.6, cool!), I didn't understand why
define version at package level If many dependencies exists to
different versions of different packages belonged to the same project,
doesn't that means (or is an indicative) that those packages should be
separeted in different projects? I don't think this constraint will be a
problem.


On Thu, Dec 21, 2017 at 12:37 PM, Sean P. DeNigris 
wrote:

> CyrilFerlicot wrote
> >> Now I got lost
>
> A ConfigurationOfXyz was doing two things:
> 1) Declaring the project structure of packages and their dependencies in a
> #baselineXyz: method
> 2) Tagging specific sets of package versions with meaning symbolic to the
> project e.g. 1.2 or stable or whatever
>
>
> CyrilFerlicot wrote
> > So, you just need Metacello to manage the dependencies... This is what
> > BaselineOf do. You just manage the dependencies part and
> > not the versionning part that is already managed by git.
>
> A BaselineOfXyz is very similar to what configurations did for #1, with a
> few simplifications (e.g. you don't need to declare the method a "baseline"
> or specify a repo because you obviously already know the repo because
> that's
> where you just got the baseline itself)
>
>
> CyrilFerlicot wrote
> > The equivalent of a ConfigurationOf version in now the SHA of a commit or
> > a tag/release
> > of git).
>
> This is mostly true, but ATM you may want to wrap your BaselineOf in a
> ConfigurationOf (i.e. refer to A with a SHA from B) for tool integration
> e.g. only Configs show up in the catalog. IIUC, one additional constraint
> to
> be aware of (not sure how important it is in practice) is that in the past
> with mcz repos, one could refer to a specific version of each package, but
> now you would only be able to specify a version for the whole git repo.
>
> HTH
>
>
>
> -
> Cheers,
> Sean
> --
> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html
>
>

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

[Vitor Medina Cruz]

But what about versioning of my external dependencies (such as other
projects)? I do that on the baseline too?

The idea in the future is to abstract versioning away from git into
Iceberg?

On Thu, Dec 21, 2017 at 11:49 AM, Cyril Ferlicot D. <
cyril.ferli...@gmail.com> wrote:

> On 21/12/2017 14:43, Vitor Medina Cruz wrote:
>
> > Now I got lost, I had understand that a ConfigurationOfXXX is my project
> > definition and that Iceberg is just the Pharo VCS (in substitution of
> > monticello). Iceberg is now my project? How do I configure my
> > dependencies, groups and versions? The Metacello documentation in Deep
> > in Pharo is deprecated for Iceberg?
> >
>
> Hi,
>
> There is two concepts to distinguish:
> - Versionning
> - Dependencies
>
> Monticello is a VCS that does not manage versionning and dependencies.
> So, you need to create a ConfigurationOfXX managing both dependencies
> (via baselines) and versionning (via configurations).
>
> Git is a VCS that manage the versionning of the project. (The equivalent
> of a ConfigurationOf version in now the SHA of a commit or a tag/release
> of git). So, you just need Metacello to manage the dependencies.
>
> This is what BaselineOf do. You just manage the dependencies part and
> not the versionning part that is already managed by git.
>
> > cheers,
> > Vitor
>
>
> --
> Cyril Ferlicot
> https://ferlicot.fr
>
> http://www.synectique.eu
> 2 rue Jacques Prévert 01,
> 59650 Villeneuve d'ascq France
>
>

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

[Cyril Ferlicot D.]

On 21/12/2017 14:43, Vitor Medina Cruz wrote:

> Now I got lost, I had understand that a ConfigurationOfXXX is my project
> definition and that Iceberg is just the Pharo VCS (in substitution of
> monticello). Iceberg is now my project? How do I configure my
> dependencies, groups and versions? The Metacello documentation in Deep
> in Pharo is deprecated for Iceberg?
> 

Hi,

There is two concepts to distinguish:
- Versionning
- Dependencies

Monticello is a VCS that does not manage versionning and dependencies.
So, you need to create a ConfigurationOfXX managing both dependencies
(via baselines) and versionning (via configurations).

Git is a VCS that manage the versionning of the project. (The equivalent
of a ConfigurationOf version in now the SHA of a commit or a tag/release
of git). So, you just need Metacello to manage the dependencies.

This is what BaselineOf do. You just manage the dependencies part and
not the versionning part that is already managed by git.

> cheers,
> Vitor


-- 
Cyril Ferlicot
https://ferlicot.fr

http://www.synectique.eu
2 rue Jacques Prévert 01,
59650 Villeneuve d'ascq France

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

[Vitor Medina Cruz]

>
> Package versions do not have any sense on iceberg, where what has sense is
> the “project” version. All packages point to a commit in repo.
>

Oh, I suspected that, but was unsure :)

the thing is: you don’t use configurations with iceberg projects, you use
> baselines.
>

Now I got lost, I had understand that a ConfigurationOfXXX is my project
definition and that Iceberg is just the Pharo VCS (in substitution of
monticello). Iceberg is now my project? How do I configure my dependencies,
groups and versions? The Metacello documentation in Deep in Pharo is
deprecated for Iceberg?

cheers,
Vitor


On Thu, Dec 21, 2017 at 9:02 AM, Esteban Lorenzano 
wrote:

>
>
> On 21 Dec 2017, at 11:03, Vitor Medina Cruz  wrote:
>
> 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
>> 
>> 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’].
>>
>
> the thing is: you don’t use configurations with iceberg projects, you use
> baselines.
>
> Esteban
>
>
> In this case  'CoolToolSet-Core-AlanJay.1' would be changed by
> 'CoolToolSet-Core-'?
>
> On Wed, Dec 20, 2017 at 6:09 PM, Stephane Ducasse  > 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 
>> 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: ; 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
>>
>>
>
>

[Pharo-users] Hi, do I nowadays need any Id and psw, to log in smalltalk hub and others?

[Janko Korelc]

... as connection time out...

Best Regards!

Janko Korelc

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

[Esteban Lorenzano]

> On 21 Dec 2017, at 11:03, Vitor Medina Cruz  wrote:
> 
> 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
> 
> 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’].

the thing is: you don’t use configurations with iceberg projects, you use 
baselines.

Esteban

> 
> In this case  'CoolToolSet-Core-AlanJay.1' would be changed by 
> 'CoolToolSet-Core-'?
> 
> On Wed, Dec 20, 2017 at 6:09 PM, Stephane Ducasse  > 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  > 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: ; 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
> 
> 

Re: [Pharo-users] Active IRC Chanel

[Esteban Lorenzano]

> On 21 Dec 2017, at 08:27, Marcus Denker  wrote:
> 
> 
> 
>> On 21 Dec 2017, at 04:34, Ian Ian  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

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

[Esteban Lorenzano]

> On 20 Dec 2017, at 19:51, Vitor Medina Cruz  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: ; 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


Hi Vitor, 

Package versions do not have any sense on iceberg, where what has sense is the 
“project” version. All packages point to a commit in repo.  

This is to say, you do not load single package in iceberg but you load a 
repository version (which is the commit). 
That’s why you use Metacello expressions like this: 

Metacello new 
repository: ‘github://someuser/someproject:sometag' 
;
baseline: ‘Blah’;
load.

and in your baselines, when you include another project you do 

spec 
baseline: ‘Blah’
with: [ spec repository: ‘github://someuser/someproject:sometag' 
 ].

cheers!
Esteban

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

[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
> 
> 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-'?

On Wed, Dec 20, 2017 at 6:09 PM, Stephane Ducasse 
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 
> 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: ; 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
>
>

Re: [Pharo-users] Athens error

[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

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

[Marcus Denker]

I added this to the Pharo news page (http://pharo.org/news 
):

[ANN] Pharo Consortium New Bronze Member: Object Profile
http://pharo.org/news/consortium-object-profile 



> On 21 Dec 2017, at 08:41, Marcus Denker  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