I thought that configurationOf what exactly to solve this kind of problem: using two different branches for to different distribution
Stef On Aug 16, 2010, at 8:32 PM, Tudor Girba wrote: > But, a simple instance variable rename would solve the problem for now. Why > is that not good enough now and then remove it later? > > Cheers, > Doru > > > On 16 Aug 2010, at 18:25, Lukas Renggli wrote: > >> 2010/8/16 Mariano Martinez Peck <[email protected]>: >>> >>> >>> On Sun, Aug 15, 2010 at 6:21 PM, Stéphane Ducasse >>> <[email protected]> wrote: >>>> >>>> this is a good question. >>>> for now I would just update the configuration to point for the repo of >>>> lukas :) >>> >>> But now for example, I need to remove the style instVar in >>> PluggableShoutMorph because in Pharo 1.2 it has already such instVar. >>> But I don't know if I can commit or if Lukas would integrate such change in >>> his repo beacuse that will break Shout to load in Pharo 1.1 (the image he >>> uses) >> >> I will fix it as soon as the PharoCore 1.2 release candidate is out >> and I am able to use the image. >> >>> so... lukas what do you think we should do? >> >> So either fix it in Pharo or create your own 'temporary' version of >> Shout in the repository where you keep all the versions for building >> the images. >> >> Lukas >> >> -- >> Lukas Renggli >> www.lukas-renggli.ch >> >> _______________________________________________ >> Pharo-project mailing list >> [email protected] >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > -- > www.tudorgirba.com > > "We cannot reach the flow of things unless we let go." > > > > > _______________________________________________ > Pharo-project mailing list > [email protected] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
