On May 9, 2009, at 6:36 PM, Alexandre Bergel wrote: > I agree with you Damien. We should not take this dangerous path. If > Pharo enhances a package picked from somewhere else, the enhancement > must be push back from where it come from.
Come on this is only possible if the changes you do don't break on other code. else people will start to complain that we are polluting the repository with pharo specific version. So either you take the time and check that this is ok (have the rights to publish, and that the version does not break on Etoy, Squeak3.8, 3.9, 3.10, croquet) and we can publish the code there. Or we don't. Now there is the HUGE question of ressources. I think that pharo is making progress and this comes at a certain prices. as we say: on ne fait pas d'omelette sans cassser d'oeuf because this applies also to SUnit and others. Stef > > > Alexandre > > > On 9 May 2009, at 18:32, Damien Pollet wrote: > >> On Sat, May 9, 2009 at 18:05, Stéphane Ducasse >> <[email protected]> wrote: >>>> There are recent versions of VB-Regex in the images, but they are >>>> not >>>> at http://www.squeaksource.com/Regex >>> >>> which images? >> >> Recent Pharo-cores >> >>>> I will copy them but that's just on of those things that make >>>> people >>>> say Pharo is not playing nice with other forks… >>> >>> we consider Regex are part of the core of pharo so what would be the >>> solution? >> >> Depends what you mean by "part of the core". >> >> If it's "included by default", then submit the fixes back to the >> original project then copy the mcz in the pharo repository if it's >> practical. >> >> If it means "part of the fork", then you take responsibility for >> maintaining your versions, but I don't see the point since it's code >> that is quite platform-agnostic, and still it would be nice to notify >> the original project (i know, it's not possible with squeaksource). >> Maybe a feature request for SourceTalk, keeping track of branches >> across repositories. >> >> -- >> Damien Pollet >> type less, do more [ | ] http://people.untyped.org/damien.pollet >> >> _______________________________________________ >> Pharo-project mailing list >> [email protected] >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > _______________________________________________ > 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
