Re: Irc

Send Pharo-users mailing list submissions to
        [hidden email]

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
        [hidden email]

You can reach the person managing the list at
        [hidden email]

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 <[hidden email]>
To: Any question about pharo is welcome <[hidden email]>
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 <[hidden email]> wrote:
>
>
>
>> On 21 Dec 2017, at 04:34, Ian Ian <[hidden email]> 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 <[hidden email]>
To: Any question about pharo is welcome <[hidden email]>
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 <[hidden email]> 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

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 <[hidden email]>
To: Any question about pharo is welcome <[hidden email]>
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 <[hidden email]> 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
<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’].

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

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

---------- Forwarded message ----------
From: Janko Korelc <[hidden email]>
To: [hidden email]
Cc: 
Bcc: 
Date: Thu, 21 Dec 2017 13:50:11 +0100
Subject: [Pharo-users] Hi, do I nowadays need any Id and psw, to log in smalltalk hub and others?

... as connection time out...

Best Regards!

Janko Korelc

---------- Forwarded message ----------
From: Vitor Medina Cruz <[hidden email]>
To: Any question about pharo is welcome <[hidden email]>
Cc: 
Bcc: 
Date: Thu, 21 Dec 2017 11:43:23 -0200
Subject: Re: [Pharo-users] Iceberg, Git and Package version

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 <[hidden email]> wrote:

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

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

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

_______________________________________________
Pharo-users mailing list
[hidden email]
http://lists.pharo.org/mailman/listinfo/pharo-users_lists.pharo.org