The problem really is the way we use metacello. As long as static versions refer to symbolic versions like #stable the problem will persist. I agree with you that there is no need to maintain a pier for pharo 2. But at the same time it should be possible load old code to build an old pier that works with older versions.Hi,There really is no point anymore in getting stuck with maintaining a development Pier version for Pharo 2. We do not have the manpower for that, and we should focus on the latest version.
Doru_______________________________________________On Tue, Apr 1, 2014 at 10:02 AM, Damien Cassou <damien.cassou@gmail.com> wrote:
On Tue, Mar 25, 2014 at 11:47 AM, Damien Cassou <damien.cassou@gmail.com> wrote:if nobody bothers having a look, I think I will just remove my email
>
> It looks related to Grease and there has been a discussion about a
> similar problem in the "Voyage cannot be load" thread of the Pharo
> mailing list. I don't know what to do and don't have time to look at
> it.
address from the Jenkins notifications because this is very annoying.
And don't tell me I should pay attention to not break Pier when making
changes to Pillar. If you don't care, why should I?
--
Damien Cassou
http://damiencassou.seasidehosting.st
"Success is the ability to go from one failure to another without
losing enthusiasm."
Winston Churchill
_______________________________________________
Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki
--"Every thing has its own flow"
Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki