Smalltalk › Frameworks & Tools › Moose

pharo5 and ConfigurationOfMagritteGlamourForPharo40

_‹ Previous Topic Next Topic _›

Classic

List

Threaded

8 messages Options

Andrei Chis

pharo5 and ConfigurationOfMagritteGlamourForPharo40

Hi,

In the latest moose image ConfigurationOfMagritteGlamourForPharo40 hides the latest versions for some packages.

For example it loads Glamour-Morphic-Renderer.issue_1126-SeanDeNigris.325 instead of the latest version Glamour-Morphic-Renderer-MarcusDenker.326.

Did something changed these days?

Cheers,

Andrei

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

Blondeau Vincent

Re: pharo5 and ConfigurationOfMagritteGlamourForPharo40

Hi,

It seems that the configuration of Magritte3 defines a dependency to MagritteGlamourForPharo40 with the version stable.

MagritteGlamourForPharo40 stable version uses <packagename>.325.

A solution is either to use the development version in Magritte3 or to release a new version in MagritteGlamourForPharo40 which will use <packagename>.326.

Cheers,

Vincent

De : [hidden email] [mailto:[hidden email]] De la part de Andrei Chis
Envoyé : vendredi 9 octobre 2015 17:43
À : Moose-related development
Objet : [Moose-dev] pharo5 and ConfigurationOfMagritteGlamourForPharo40

Hi,

In the latest moose image ConfigurationOfMagritteGlamourForPharo40 hides the latest versions for some packages.

For example it loads Glamour-Morphic-Renderer.issue_1126-SeanDeNigris.325 instead of the latest version Glamour-Morphic-Renderer-MarcusDenker.326.

Did something changed these days?

Cheers,

Andrei

Ce message et les pièces jointes sont confidentiels et réservés à l'usage exclusif de ses destinataires. Il peut également être protégé par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir immédiatement l'expéditeur et de le détruire. L'intégrité du message ne pouvant être assurée sur Internet, la responsabilité de Worldline ne pourra être recherchée quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne saurait être recherchée pour tout dommage résultant d'un virus transmis.

This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Worldline liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.

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

Sean P. DeNigris

Re: pharo5 and ConfigurationOfMagritteGlamourForPharo40

Administrator

In reply to this post by Andrei Chis

Andrei Chis wrote

In the latest moose image ConfigurationOfMagritteGlamourForPharo40 hides
the latest versions for some packages.

Sorry for the confusion. The only purpose of this configuration is to ease the pain of Moose and Pharo both evolving rapidly and independently. The idea was to have some post-Pharo-40 Moose enhancements available in Pharo 40, specifically because they were needed for some Magritte enhancements I did. In Pharo 5.0, there should be no need to load this config because we can just integrate the Moose enhancements. Although, since a) some things, like the Issue 1126 you mentioned are WIP, and b) I'm not yet using Pharo 5.0, maybe I'm missing something...

Cheers,
Sean

Stephan Eggermont-3

Re: pharo5 and ConfigurationOfMagritteGlamourForPharo40

Hi Sean,

I don't understand at all why that needs a separate configuration.

Stephan

On 10-10-15 16:43, Sean P. DeNigris wrote:

> Andrei Chis wrote
>> In the latest moose image ConfigurationOfMagritteGlamourForPharo40 hides
>> the latest versions for some packages.
> Sorry for the confusion. The only purpose of this configuration is to ease
> the pain of Moose and Pharo both evolving rapidly and independently. The
> idea was to have some post-Pharo-40 Moose enhancements available in Pharo
> 40, specifically because they were needed for some Magritte enhancements I
> did. In Pharo 5.0, there should be no need to load this config because we
> can just integrate the Moose enhancements. Although, since a) some things,
> like the Issue 1126 you mentioned are WIP, and b) I'm not yet using Pharo
> 5.0, maybe I'm missing something...
>
>
>
> -----
> Cheers,
> Sean
> --
> View this message in context: http://forum.world.st/pharo5-and-ConfigurationOfMagritteGlamourForPharo40-tp4854773p4854878.html
> Sent from the Moose mailing list archive at Nabble.com.
> _______________________________________________
> 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: pharo5 and ConfigurationOfMagritteGlamourForPharo40

Let's see if this helps

Name: ConfigurationOfMagritte3-StephanEggermont.117
Author: StephanEggermont
Time: 10 October 2015, 5:56:07.098168 pm
UUID: e61105b7-4521-4428-9881-795f10251beb
Ancestors: ConfigurationOfMagritte3-SeanDeNigris.116

In place change: block with MagritteGlamourForPharo40 only for Pharo 4.
_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

Sean P. DeNigris

Re: pharo5 and ConfigurationOfMagritteGlamourForPharo40

Administrator

In reply to this post by Stephan Eggermont-3

Stephan Eggermont wrote

I don't understand at all why that needs a separate configuration.

IIRC it was because Moose beta parallels Pharo beta, so latest Moose changes are (potentially) incompatible with Pharo 4.0.

Cheers,
Sean

Stephan Eggermont-3

Re: pharo5 and ConfigurationOfMagritteGlamourForPharo40

On 10-10-15 19:34, Sean P. DeNigris wrote:
> Stephan Eggermont wrote
>> I don't understand at all why that needs a separate configuration.
> IIRC it was because Moose beta parallels Pharo beta, so latest Moose changes
> are (potentially) incompatible with Pharo 4.0.

So why does that need a separate configuration?

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

Sean P. DeNigris

Re: pharo5 and ConfigurationOfMagritteGlamourForPharo40

Administrator

Stephan Eggermont wrote

So why does that need a separate configuration?

Maybe it doesn't.

I remember trying to update the existing configurations, but there were at least three or four configs involved (e.g. Glamour, GlamourCore, GT-Xyz, etc.), some of which had already created new Pharo-5.0-specific versions. For one thing, it quickly seemed too complex for me, and for another, I wasn't sure e.g. if x.x.x was released with Pharo 4.0, and x.x.(x+1) was Pharo 5.0-specific, what I would call the newer 4.0-specific one.

If someone can figure out how to do it better, I'm not attached to this method. It was primarily to get on with my own work in Pharo 4.0.

Cheers,
Sean