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. Alexandre On 9 May 2009, at 18:32, Damien Pollet wrote:
On Sat, May 9, 2009 at 18:05, Stéphane Ducasse <stephane.ducasse@inria.fr> 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 Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.