Why you just adapt your package to the version of pharo that includes the changes. We do that all the time so I do not understand where is the problem?
>> - If included with Pharo I suggest to rename all the methods, >> otherwise we will run into big troubles with Seaside and other >> projects that depend on Grease. >> >> >> From a philosophical standpoint, I *hate* that. this means that as a >> plattform, we can not >> grow and improve our libraris anymore? >> Shouldn't be the goal that useful extensions gets adopted by the core? > > I agree, from Pharo point of view. However, for any software built on > top of Pharo it means troubles if Pharo suddenly implements the same > methods. > > Lukas > > -- > Lukas Renggli > www.lukas-renggli.ch > > _______________________________________________ > 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
