Smalltalk › Frameworks & Tools › Moose

Roassal2 / Pharo 4.0

_‹ Previous Topic Next Topic _›

Classic

List

Threaded

30 messages Options

Offray

Re: Roassal2 / Pharo 4.0

Thanks Alexandre, I can confirm this works! Now I have examples back :-)

Cheers,

Offray

On 24/09/15 17:30, Alexandre Bergel wrote:

> Hi Volkert and Johan,
>
> I think a wrong version of Roassal was chosen. I fixed the configuration.
> Try in Pharo 4.0:
>
> Gofer it
> smalltalkhubUser: 'ObjectProfile' project: 'Roassal2';
> configurationOf: 'Roassal2';
> loadVersion: ‘1.15'
>
> It should work. And you have even the example browser!
>
> Cheers,
> Alexandre
>
>
>> On Sep 24, 2015, at 12:16 PM, Volkert <[hidden email]> wrote:
>>
>> Roassal2 (stable) does not load into Pharo 4.0 anymore:-(
>>
>> Too bad that Pharo is so instable ...
>>
>> Volkert
>>
>> <ijddbdgd.png>
>> _______________________________________________
>> Moose-dev mailing list
>> [hidden email]
>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

Offray

Re: Roassal2 / Pharo 4.0

In reply to this post by Peter Uhnak

Agree! Last week we had a workshop on our hackerspace and the Roassal2 examples on Pharo 4 were broken. If I run:

Gofer it
smalltalkhubUser: 'ObjectProfile' project: 'Roassal2';
configurationOf: 'Roassal2';
loadStable.

on pharo 4, Roassal examples don't work, while running it with loadVersion: '1.15' works. Shouldn't loadStable point to '1.15' or the last version which works on Pharo 4?

Cheers,

Offray

On 25/09/15 05:08, Peter Uhnák wrote:

There should be CI job for Roassal2 #stable and Pharo4.
Especially if most of Roassal contributors/devs are in Pharo 5 and thus only end-users will notice it.

(with the multi-configuration job in Jenkins it's easy to setup custom matrix)

Peter

On Fri, Sep 25, 2015 at 11:37 AM, Tudor Girba <[hidden email]> wrote:

Thanks for your patience, Volkert.

And thanks Alex for fixing the configuration.

Cheers,

Doru

On Fri, Sep 25, 2015 at 10:30 AM, Volkert <[hidden email]> wrote:

On <a moz-do-not-send="true" href="tel:25.09.2015%2007" value="+12509201507" target="_blank">25.09.2015 07:52, Sven Van Caekenberghe wrote:

On 25 Sep 2015, at 05:18, Volkert <[hidden email]> wrote:

But how do i figure out, which is the right Version for Pharo 4.0? I always thought loadStable is ok, as mentioned http://objectprofile.com/Roassal.html.

You are right, as an end user you should just use #stable on any supported platform and it should work.

The authors of the configuration can declare for each platform (Pharo 4, 5) which is the stable version.

Obviously someone made a mistake while moving forward, we are all humans after all.

i have no intention to blame here someone ... i only try to understand how the things are connected ... and i have learned something new ...

Volkert

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

--

www.tudorgirba.com

"Every thing has its own flow"

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

abergel

Re: Roassal2 / Pharo 4.0

I have no idea how to do it. I have tried:

stable: spec
<symbolicVersion: #'stable'>

spec for: #'common' version: '1.16'.
spec for: #'pharo4.x' version: '1.15'.
spec for: #'pharo3.x' version: '1.6'.
spec for: #'pharo5.x' version: '1.16’.

But loading:
Gofer it
smalltalkhubUser: 'ObjectProfile' project: 'Roassal2';
configurationOf: 'Roassal2';
loadStable

in pharo 4 still produces the error.

Alexandre

> On Sep 28, 2015, at 5:23 PM, Offray Vladimir Luna Cárdenas <[hidden email]> wrote:
>
> Agree! Last week we had a workshop on our hackerspace and the Roassal2 examples on Pharo 4 were broken. If I run:
>
> Gofer it
> smalltalkhubUser: 'ObjectProfile' project: 'Roassal2';
> configurationOf: 'Roassal2';
> loadStable.
>
> on pharo 4, Roassal examples don't work, while running it with loadVersion: '1.15' works. Shouldn't loadStable point to '1.15' or the last version which works on Pharo 4?
>
> Cheers,
>
> Offray
>
> On 25/09/15 05:08, Peter Uhnák wrote:
>> There should be CI job for Roassal2 #stable and Pharo4.
>> Especially if most of Roassal contributors/devs are in Pharo 5 and thus only end-users will notice it.
>>
>> (with the multi-configuration job in Jenkins it's easy to setup custom matrix)
>>
>> Peter
>>
>> On Fri, Sep 25, 2015 at 11:37 AM, Tudor Girba <[hidden email]> wrote:
>> Thanks for your patience, Volkert.
>>
>> And thanks Alex for fixing the configuration.
>>
>> Cheers,
>> Doru
>>
>>
>> On Fri, Sep 25, 2015 at 10:30 AM, Volkert <[hidden email]> wrote:
>> On 25.09.2015 07:52, Sven Van Caekenberghe wrote:
>> On 25 Sep 2015, at 05:18, Volkert <[hidden email]> wrote:
>>
>> But how do i figure out, which is the right Version for Pharo 4.0? I always thought loadStable is ok, as mentioned http://objectprofile.com/Roassal.html.
>> You are right, as an end user you should just use #stable on any supported platform and it should work.
>>
>> The authors of the configuration can declare for each platform (Pharo 4, 5) which is the stable version.
>>
>> Obviously someone made a mistake while moving forward, we are all humans after all.
>> i have no intention to blame here someone ... i only try to understand how the things are connected ... and i have learned something new ...
>>
>> Volkert
>>
>>
>>
>> _______________________________________________
>> Moose-dev mailing list
>> [hidden email]
>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>>
>> _______________________________________________
>> Moose-dev mailing list
>> [hidden email]
>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>>
>>
>>
>> --
>> www.tudorgirba.com
>>
>> "Every thing has its own flow"
>>
>> _______________________________________________
>> Moose-dev mailing list
>> [hidden email]
>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>>
>>
>>
>>
>> _______________________________________________
>> Moose-dev mailing list
>>
>> [hidden email]
>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev

--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

abergel

Re: Roassal2 / Pharo 4.0

In reply to this post by Sven Van Caekenberghe-2

Yeah, it would be great to have this behavior. But no idea how.

I tried to have in ConfigurationOfRoassal2:

stable: spec
<symbolicVersion: #'stable'>

spec for: #'common' version: '1.16'.
spec for: #'pharo4.x' version: '1.15'.
spec for: #'pharo3.x' version: '1.6'.
spec for: #'pharo5.x' version: '1.16’.

But loading:
Gofer it
smalltalkhubUser: 'ObjectProfile' project: 'Roassal2';
configurationOf: 'Roassal2';
loadStable

in pharo 4 still produces the error.

Alexandre

> On Sep 25, 2015, at 7:52 AM, Sven Van Caekenberghe <[hidden email]> wrote:
>
>
>> On 25 Sep 2015, at 05:18, Volkert <[hidden email]> wrote:
>>
>> But how do i figure out, which is the right Version for Pharo 4.0? I always thought loadStable is ok, as mentioned http://objectprofile.com/Roassal.html.
>
> You are right, as an end user you should just use #stable on any supported platform and it should work.
>
> The authors of the configuration can declare for each platform (Pharo 4, 5) which is the stable version.
>
> Obviously someone made a mistake while moving forward, we are all humans after all.
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev

volkert-2

Re: Roassal2 / Pharo 4.0

Now version 1.15 produce the warning as well :-(

On 28.09.2015 20:43, Alexandre Bergel wrote:

Yeah, it would be great to have this behavior. But no idea how.

I tried to have in ConfigurationOfRoassal2:

stable: spec
	<symbolicVersion: #'stable'>

	spec for: #'common' version: '1.16'.
	spec for: #'pharo4.x' version: '1.15'.
	spec for: #'pharo3.x' version: '1.6'.
	spec for: #'pharo5.x' version: '1.16’.

But loading:
Gofer it
   smalltalkhubUser: 'ObjectProfile' project: 'Roassal2';
   configurationOf: 'Roassal2';
   loadStable

in pharo 4 still produces the error.

Alexandre

On Sep 25, 2015, at 7:52 AM, Sven Van Caekenberghe [hidden email] wrote:

On 25 Sep 2015, at 05:18, Volkert [hidden email] wrote:

But how do i figure out, which is the right Version for Pharo 4.0? I always thought loadStable is ok, as mentioned http://objectprofile.com/Roassal.html.

You are right, as an end user you should just use #stable on any supported platform and it should work.

The authors of the configuration can declare for each platform (Pharo 4, 5) which is the stable version.

Obviously someone made a mistake while moving forward, we are all humans after all.
_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

philippeback

Re: Roassal2 / Pharo 4.0

Same here.

On Wed, Sep 30, 2015 at 7:38 AM, Volkert <[hidden email]> wrote:

Now version 1.15 produce the warning as well :-(

On 28.09.2015 20:43, Alexandre Bergel wrote:

Yeah, it would be great to have this behavior. But no idea how.

I tried to have in ConfigurationOfRoassal2:

stable: spec
	<symbolicVersion: #'stable'>

	spec for: #'common' version: '1.16'.
	spec for: #'pharo4.x' version: '1.15'.
	spec for: #'pharo3.x' version: '1.6'.
	spec for: #'pharo5.x' version: '1.16’.

But loading:
Gofer it
   smalltalkhubUser: 'ObjectProfile' project: 'Roassal2';
   configurationOf: 'Roassal2';
   loadStable

in pharo 4 still produces the error.

Alexandre

On Sep 25, 2015, at 7:52 AM, Sven Van Caekenberghe [hidden email] wrote:

On 25 Sep 2015, at 05:18, Volkert [hidden email] wrote:

But how do i figure out, which is the right Version for Pharo 4.0? I always thought loadStable is ok, as mentioned http://objectprofile.com/Roassal.html.

You are right, as an end user you should just use #stable on any supported platform and it should work.

The authors of the configuration can declare for each platform (Pharo 4, 5) which is the stable version.

Obviously someone made a mistake while moving forward, we are all humans after all.
_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

abergel

Re: Roassal2 / Pharo 4.0

Sorry guys for this regression.
I have reverted the configuration. It is really mysterious how it works.

So, in summary, to load Roassal on Pharo 4 you need to do:
Gofer it
smalltalkhubUser: 'ObjectProfile' project: 'Roassal2';
configurationOf: 'Roassal2';
loadVersion: '1.15'.

Cheers,
Alexandre

> On Sep 30, 2015, at 9:15 AM, [hidden email] wrote:
>
> Same here.
>
> On Wed, Sep 30, 2015 at 7:38 AM, Volkert <[hidden email]> wrote:
> Now version 1.15 produce the warning as well :-(
>
>
> <begfacfh.png>
>
>
>
> On 28.09.2015 20:43, Alexandre Bergel wrote:
>> Yeah, it would be great to have this behavior. But no idea how.
>>
>> I tried to have in ConfigurationOfRoassal2:
>>
>> stable: spec
>> <symbolicVersion: #'stable'>
>>
>> spec for: #'common' version: '1.16'.
>> spec for: #'pharo4.x' version: '1.15'.
>> spec for: #'pharo3.x' version: '1.6'.
>> spec for: #'pharo5.x' version: '1.16’.
>>
>> But loading:
>> Gofer it
>> smalltalkhubUser: 'ObjectProfile' project: 'Roassal2';
>> configurationOf: 'Roassal2';
>> loadStable
>>
>> in pharo 4 still produces the error.
>>
>> Alexandre
>>
>>
>>
>>> On Sep 25, 2015, at 7:52 AM, Sven Van Caekenberghe <[hidden email]>
>>> wrote:
>>>
>>>
>>>
>>>> On 25 Sep 2015, at 05:18, Volkert <[hidden email]>
>>>> wrote:
>>>>
>>>> But how do i figure out, which is the right Version for Pharo 4.0? I always thought loadStable is ok, as mentioned
>>>> http://objectprofile.com/Roassal.html
>>>> .
>>>>
>>> You are right, as an end user you should just use #stable on any supported platform and it should work.
>>>
>>> The authors of the configuration can declare for each platform (Pharo 4, 5) which is the stable version.
>>>
>>> Obviously someone made a mistake while moving forward, we are all humans after all.
>>> _______________________________________________
>>> Moose-dev mailing list
>>>
>>> [hidden email]
>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>
>
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>
>
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev

volkert-2

Re: Roassal2 / Pharo 4.0

Now is fine again ... :-)

... i will try to understand how Configuration stuff works. Will first
read "Deep into Pharo" today ...

BW,
Volkert

On 30.09.2015 10:45, Alexandre Bergel wrote:

> Sorry guys for this regression.
> I have reverted the configuration. It is really mysterious how it works.
>
> So, in summary, to load Roassal on Pharo 4 you need to do:
> Gofer it
> smalltalkhubUser: 'ObjectProfile' project: 'Roassal2';
> configurationOf: 'Roassal2';
> loadVersion: '1.15'.
>
> Cheers,
> Alexandre
>
>
>
>> On Sep 30, 2015, at 9:15 AM, [hidden email] wrote:
>>
>> Same here.
>>
>> On Wed, Sep 30, 2015 at 7:38 AM, Volkert <[hidden email]> wrote:
>> Now version 1.15 produce the warning as well :-(
>>
>>
>> <begfacfh.png>
>>
>>
>>
>> On 28.09.2015 20:43, Alexandre Bergel wrote:
>>> Yeah, it would be great to have this behavior. But no idea how.
>>>
>>> I tried to have in ConfigurationOfRoassal2:
>>>
>>> stable: spec
>>> <symbolicVersion: #'stable'>
>>>
>>> spec for: #'common' version: '1.16'.
>>> spec for: #'pharo4.x' version: '1.15'.
>>> spec for: #'pharo3.x' version: '1.6'.
>>> spec for: #'pharo5.x' version: '1.16’.
>>>
>>> But loading:
>>> Gofer it
>>> smalltalkhubUser: 'ObjectProfile' project: 'Roassal2';
>>> configurationOf: 'Roassal2';
>>> loadStable
>>>
>>> in pharo 4 still produces the error.
>>>
>>> Alexandre
>>>
>>>
>>>
>>>> On Sep 25, 2015, at 7:52 AM, Sven Van Caekenberghe <[hidden email]>
>>>> wrote:
>>>>
>>>>
>>>>
>>>>> On 25 Sep 2015, at 05:18, Volkert <[hidden email]>
>>>>> wrote:
>>>>>
>>>>> But how do i figure out, which is the right Version for Pharo 4.0? I always thought loadStable is ok, as mentioned
>>>>> http://objectprofile.com/Roassal.html
>>>>> .
>>>>>
>>>> You are right, as an end user you should just use #stable on any supported platform and it should work.
>>>>
>>>> The authors of the configuration can declare for each platform (Pharo 4, 5) which is the stable version.
>>>>
>>>> Obviously someone made a mistake while moving forward, we are all humans after all.
>>>> _______________________________________________
>>>> Moose-dev mailing list
>>>>
>>>> [hidden email]
>>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>>
>> _______________________________________________
>> Moose-dev mailing list
>> [hidden email]
>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>>
>>
>> _______________________________________________
>> Moose-dev mailing list
>> [hidden email]
>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

philippeback

Re: Roassal2 / Pharo 4.0

Why not put a version of the config in the Pharo40Metarepo and leave it at that?

As the new stuff occurs in Pharo5, new configs should go in a Pharo50Metarepo and not affect anything in 4.0

Feeback welcome.

Phil

On Wed, Sep 30, 2015 at 10:57 AM, Volkert <[hidden email]> wrote:

Now is fine again ... :-)

... i will try to understand how Configuration stuff works. Will first read "Deep into Pharo" today ...

BW,
Volkert

On 30.09.2015 10:45, Alexandre Bergel wrote:

Sorry guys for this regression.
I have reverted the configuration. It is really mysterious how it works.

So, in summary, to load Roassal on Pharo 4 you need to do:
Gofer it
smalltalkhubUser: 'ObjectProfile' project: 'Roassal2';
configurationOf: 'Roassal2';
loadVersion: '1.15'.

Cheers,
Alexandre

On Sep 30, 2015, at 9:15 AM, [hidden email] wrote:

Same here.

On Wed, Sep 30, 2015 at 7:38 AM, Volkert <[hidden email]> wrote:
Now version 1.15 produce the warning as well :-(

<begfacfh.png>

On 28.09.2015 20:43, Alexandre Bergel wrote:

Yeah, it would be great to have this behavior. But no idea how.

I tried to have in ConfigurationOfRoassal2:

stable: spec
<symbolicVersion: #'stable'>

spec for: #'common' version: '1.16'.
spec for: #'pharo4.x' version: '1.15'.
spec for: #'pharo3.x' version: '1.6'.
spec for: #'pharo5.x' version: '1.16’.

But loading:
Gofer it
smalltalkhubUser: 'ObjectProfile' project: 'Roassal2';
configurationOf: 'Roassal2';
loadStable

in pharo 4 still produces the error.

Alexandre

On Sep 25, 2015, at 7:52 AM, Sven Van Caekenberghe <[hidden email]>
wrote:

On 25 Sep 2015, at 05:18, Volkert <[hidden email]>
wrote:

But how do i figure out, which is the right Version for Pharo 4.0? I always thought loadStable is ok, as mentioned
http://objectprofile.com/Roassal.html
.

You are right, as an end user you should just use #stable on any supported platform and it should work.

The authors of the configuration can declare for each platform (Pharo 4, 5) which is the stable version.

Obviously someone made a mistake while moving forward, we are all humans after all.
_______________________________________________
Moose-dev mailing list

[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

Stephan Eggermont-3

Re: Roassal2 / Pharo 4.0

On 30/09/15 15:10, [hidden email] wrote:
> Why not put a version of the config in the Pharo40Metarepo and leave
> it at that?
>
> As the new stuff occurs in Pharo5, new configs should go in a
> Pharo50Metarepo and not affect anything in 4.0
>
> Feeback welcome.

We will have a year of bug fixes in Pharo 4. The core development moves
to Pharo 5, and not all other projects do the same. Lots of projects
want to be a bit behind the bleeding edge, or even only build on
released versions. A Configuration describes how to load things in each
version of Pharo/Gemstone/Squeak (that the project wants to support).
Projects that do not want to be on the bleeding edge still want bug
fixes. That means they always want the latest version of every
configurationOf they use (not necessarily the latest version found in
that configurationOf, though).

If the development of a dependency happens in Pharo 5 and only bugfixes
are backported to Pharo 4, it is fine to depend on the latest released
version on Pharo 4 (that can be #'stable') as long as the bugfixes don't
affect the api you use. This only works if that also goes for the
dependencies of the dependency etc...

If the development of a dependency happens in Pharo 4 or both 4 and 5,
the dependency needs to release a symbolic version that marks the
version at the time of the Pharo 4 release. That can be updated with
non-breaking fixes.

What we now see is GlamourCore depending on an old version of Rubric,
and Roassal2 depending on GlamourCore. Three different projects are now
hard connected to each other with the numbered versions. Breaking that
hard dependency would help. That might need adding symbolic versions to
Rubric.

Another issue is the old configurations in the Pharo 4 build. I'm not
sure why they are not updated.

Stephan

Stephan
_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev