[Pharo-project] Monticello configuration still broken
I try to load Magma r41.1 throught Monticello configuration. This last one is still broken in Pharo and I need to apply the usual fixes MonticelloConfigurations-cmm.44.mcz, Monticello-SR.315.mcz to get it loaded (was previously reported). For Pharo to be a developer friendly environment, it is a must to include these fixes, even waiting for a better solution, because newbies will get burn there. -- http://blog.ofset.org/hilaire
Thanks for reporting. I created http://code.google.com/p/pharo/issues/detail?id=368 Adrian On Dec 2, 2008, at 14:11 , Hilaire Fernandes wrote:
I try to load Magma r41.1 throught Monticello configuration. This last one is still broken in Pharo and I need to apply the usual fixes MonticelloConfigurations-cmm.44.mcz, Monticello-SR.315.mcz to get it loaded (was previously reported).
For Pharo to be a developer friendly environment, it is a must to include these fixes, even waiting for a better solution, because newbies will get burn there.
-- http://blog.ofset.org/hilaire
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
On Tue, Dec 2, 2008 at 2:11 PM, Hilaire Fernandes <hilaire@ofset.org> wrote:
For Pharo to be a developer friendly environment, it is a must to include these fixes, even waiting for a better solution, because newbies will get burn there.
MC1.5 already fixes all issues and I think it would be better to integrate it than recreating it. -- Damien Cassou http://damiencassou.seasidehosting.st
No, installation of Magma through SqueakMap has MC1.5 as a prerequisite, and it does not work on Pharo (I sent a previous post but it was blocked because of the screenshot size, I will resent it again) Hilaire 2008/12/2 Damien Cassou <damien.cassou@gmail.com>:
On Tue, Dec 2, 2008 at 2:11 PM, Hilaire Fernandes <hilaire@ofset.org> wrote:
For Pharo to be a developer friendly environment, it is a must to include these fixes, even waiting for a better solution, because newbies will get burn there.
MC1.5 already fixes all issues and I think it would be better to integrate it than recreating it.
-- Damien Cassou http://damiencassou.seasidehosting.st
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
It depends on what is inside MC1.5 When you load a package you load all the extensions. Stef On Dec 2, 2008, at 2:41 PM, Damien Cassou wrote:
On Tue, Dec 2, 2008 at 2:11 PM, Hilaire Fernandes <hilaire@ofset.org> wrote:
For Pharo to be a developer friendly environment, it is a must to include these fixes, even waiting for a better solution, because newbies will get burn there.
MC1.5 already fixes all issues and I think it would be better to integrate it than recreating it.
-- Damien Cassou http://damiencassou.seasidehosting.st
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Stéphane Ducasse wrote:
It depends on what is inside MC1.5 It should not. When you load a package you load all the extensions. When you load a package like MC1.5 you are buying into to the philosophy, you would be joining a collaborative venture to benefit all.
The philosophy being that it should work for as many people as possible, be as backwardly compatible as possible, incorporate as many fixes as possible for everyone and provide a basis for moving forward. If within the actual code there is something you dont like then you can join in with the effort and fix it, because it is a collaborative effort moving forward. Keith
Yes but when we load a package we load the package and its extensions and in Pharo we take care about that. Stef On Dec 3, 2008, at 12:02 AM, Keith Hodges wrote:
Stéphane Ducasse wrote:
It depends on what is inside MC1.5 It should not. When you load a package you load all the extensions. When you load a package like MC1.5 you are buying into to the philosophy, you would be joining a collaborative venture to benefit all.
The philosophy being that it should work for as many people as possible, be as backwardly compatible as possible, incorporate as many fixes as possible for everyone and provide a basis for moving forward.
If within the actual code there is something you dont like then you can join in with the effort and fix it, because it is a collaborative effort moving forward.
Keith
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Because we did not have the time (and nobody took the time to look at the code and write a report for us on the extensions and status of MC1.5 and MC1.6) This is on the pipeline like SUnit+ and KernelExtensions. Now december is a ***terrible*** for researchers in France and I cannot cut myself in more slices than already done. Stef On Dec 3, 2008, at 10:20 PM, Keith Hodges wrote:
Stéphane Ducasse wrote:
Yes but when we load a package we load the package and its extensions and in Pharo we take care about that.
Stef So why do you stick with a broken MC then?
Keith
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
On Wed, Dec 03, 2008 at 10:24:55PM +0100, St?phane Ducasse wrote:
Because we did not have the time (and nobody took the time to look at the code and write a report for us on the extensions and status of MC1.5 and MC1.6)
I'll take care of this. I am going to write up documentation and changes, and some tests for the new features of MC1.5/1.6 when I release mc1.6. I'm gonna make a real release out of 1.6 once I finish SystemEditor, and overhaul the MC/OB integration. I also think I'll try running the entire pharo update stream (minus mc changes) through a 3.9.1 + mc1.6. I think that should be good enough for you. I should have this ready in 2 or 3 months. In the meantime, MC1.0 is working just fine. I've already merged in most of pharo's mc changes into 1.5. -- Matthew Fulmer -- http://mtfulmer.wordpress.com/
Cool Don't get me wrong we are not against keith and you. We are just cautious. We are building Pharo and we do not want to destroy it with not clear extensions and "just package loading....It is easy it is a package" Stef On Dec 4, 2008, at 12:12 AM, Matthew Fulmer wrote:
On Wed, Dec 03, 2008 at 10:24:55PM +0100, St?phane Ducasse wrote:
Because we did not have the time (and nobody took the time to look at the code and write a report for us on the extensions and status of MC1.5 and MC1.6)
I'll take care of this. I am going to write up documentation and changes, and some tests for the new features of MC1.5/1.6 when I release mc1.6. I'm gonna make a real release out of 1.6 once I finish SystemEditor, and overhaul the MC/OB integration. I also think I'll try running the entire pharo update stream (minus mc changes) through a 3.9.1 + mc1.6. I think that should be good enough for you. I should have this ready in 2 or 3 months. In the meantime, MC1.0 is working just fine. I've already merged in most of pharo's mc changes into 1.5.
-- Matthew Fulmer -- http://mtfulmer.wordpress.com/
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
On Thu, Dec 4, 2008 at 12:12 AM, Matthew Fulmer <tapplek@gmail.com> wrote:
I'll take care of this. I am going to write up documentation and changes, and some tests for the new features of MC1.5/1.6 when I release mc1.6. I'm gonna make a real release out of 1.6 once I finish SystemEditor, and overhaul the MC/OB integration. I also think I'll try running the entire pharo update stream (minus mc changes) through a 3.9.1 + mc1.6. I think that should be good enough for you. I should have this ready in 2 or 3 months. In the meantime, MC1.0 is working just fine. I've already merged in most of pharo's mc changes into 1.5.
Thank you very much Matthew and Keith. -- Damien Cassou http://damiencassou.seasidehosting.st
participants (6)
-
Adrian Lienhard -
Damien Cassou -
Hilaire Fernandes -
Keith Hodges -
Matthew Fulmer -
Stéphane Ducasse