...@lists.pharo.org
mailto:pharo-dev-boun...@lists.pharo.org] de la part de Stéphane
Ducasse [stephane.duca...@inria.fr mailto:stephane.duca...@inria.fr]
Date d'envoi : mercredi 19 juin 2013 21:21
À : Pharo Development List
Objet : Re: [Pharo-dev] you may need to update your
De : Pharo-dev [pharo-dev-boun...@lists.pharo.org] de la part de Stéphane
Ducasse [stephane.duca...@inria.fr]
Date d'envoi : mercredi 19 juin 2013 21:21
À : Pharo Development List
Objet : Re: [Pharo-dev] you may need to update your configurations
Christophe.
[1
Hello,
Since the update #30205, Pharo 3.0 will not be recognized anymore as a Pharo
2.0 platform (from the metacello point of view).
It means that if you have specific pharo 2.0 instructions in your
configurations and you want to work on Pharo 3.0, you should add pharo 3.0
support in the
Cool.
Side question: Christophe, are you working on utf8 support for the
Monticello tools? I encountered encoding problems with ZipArchive.
Thierry
Le 19/06/2013 13:53, Christophe Demarey a écrit :
Hello,
Since the update #30205, Pharo 3.0 will not be recognized anymore as a
Pharo 2.0
Le 19 juin 2013 à 14:45, Goubier Thierry a écrit :
Cool.
Side question: Christophe, are you working on utf8 support for the Monticello
tools? I encountered encoding problems with ZipArchive.
Not at all. There is some work from Nicolas integrated [1] but I'm not aware of
other work on
Le 19/06/2013 16:17, Christophe Demarey a écrit :
Le 19 juin 2013 à 14:45, Goubier Thierry a écrit :
Cool.
Side question: Christophe, are you working on utf8 support for the
Monticello tools? I encountered encoding problems with ZipArchive.
Not at all. There is some work from Nicolas
Le 19/06/2013 16:46, Esteban Lorenzano a écrit :
important bugfixes can be integrated in 2.0, is not all white and black :)
Thanks, you're right of course :)
Thierry
On Jun 19, 2013, at 4:36 PM, Goubier Thierry thierry.goub...@cea.fr wrote:
Le 19/06/2013 16:17, Christophe Demarey a
Le 19 juin 2013 à 16:36, Goubier Thierry a écrit :
By the way, why the change in MonticelloFileTree-Core-ChristopheDemarey.97
breaks Pharo 2.0 ?
Because this change comes from the FileTree branch used fro Pharo3 [1].
This small change avoid to use a deprecated method in Pharo3.
It should
important bugfixes can be integrated in 2.0, is not all white and black :)
On Jun 19, 2013, at 4:36 PM, Goubier Thierry thierry.goub...@cea.fr wrote:
Le 19/06/2013 16:17, Christophe Demarey a écrit :
Le 19 juin 2013 à 14:45, Goubier Thierry a écrit :
Cool.
Side question:
Christophe.
[1] https://pharo.fogbugz.com/default.asp?10801
Ouch. Does not bode too well for backporting that to Pharo 2.0.
I'm feeling a bit down. It's either enduring bugs in 2.0 for a year or so or
fighting every few days with 3.0 and knowing that anyway it's not production
De : Pharo-dev [pharo-dev-boun...@lists.pharo.org] de la part de Stéphane
Ducasse [stephane.duca...@inria.fr]
Date d'envoi : mercredi 19 juin 2013 21:21
À : Pharo Development List
Objet : Re: [Pharo-dev] you may need to update your configurations
: mercredi 19 juin 2013 21:21
À : Pharo Development List
Objet : Re: [Pharo-dev] you may need to update your configurations
Christophe.
[1] https://pharo.fogbugz.com/default.asp?10801
Ouch. Does not bode too well for backporting that to Pharo 2.0.
I'm feeling a bit down. It's
[stephane.duca...@inria.fr]
Date d'envoi : mercredi 19 juin 2013 21:21
À : Pharo Development List
Objet : Re: [Pharo-dev] you may need to update your configurations
Christophe.
[1] https://pharo.fogbugz.com/default.asp?10801
Ouch. Does not bode too well for backporting that to Pharo 2.0
[pharo-dev-boun...@lists.pharo.org] de la part de Stéphane
Ducasse [stephane.duca...@inria.fr]
Date d'envoi : mercredi 19 juin 2013 21:21
À : Pharo Development List
Objet : Re: [Pharo-dev] you may need to update your configurations
Christophe.
[1] https://pharo.fogbugz.com
: Pharo-dev [pharo-dev-boun...@lists.pharo.org] de la part de
Stéphane Ducasse [stephane.duca...@inria.fr]
Date d'envoi : mercredi 19 juin 2013 21:21
À : Pharo Development List
Objet : Re: [Pharo-dev] you may need to update your configurations
Christophe.
[1] https
Ducasse [stephane.duca...@inria.fr]
Date d'envoi : mercredi 19 juin 2013 21:21
À : Pharo Development List
Objet : Re: [Pharo-dev] you may need to update your configurations
Christophe.
[1] https://pharo.fogbugz.com/default.asp?10801
Ouch. Does not bode too well
] you may need to update your configurations
Christophe.
[1] https://pharo.fogbugz.com/default.asp?10801
Ouch. Does not bode too well for backporting that to Pharo 2.0.
I'm feeling a bit down. It's either enduring bugs in 2.0 for a year
or so or fighting every
, 2013 8:15:48 AM
| Subject: Re: [Pharo-dev] you may need to update your configurations
|
|
|
| Le 19/06/2013 17:01, Christophe Demarey a écrit :
|
| Le 19 juin 2013 à 16:36, Goubier Thierry a écrit :
|
| By the way, why the change in
| MonticelloFileTree-Core-ChristopheDemarey.97 breaks Pharo
18 matches
Mail list logo
