Metacello will be used to identify stable versions of the packages that are known to work and there is an ongoing effort to create Metacello configurations for all of the projects that go into the dev and web images. So that part of the puzzle is being addressed. Dale ----- "Mariano Martinez Peck" <marianopeck@gmail.com> wrote: | Thanks Lukas to be agree. I like your scripts, but the problem is that | you | use your own forked repository to get an stable version. I would love | to | have THAT, but in the original repositories. Examples: omnibrowser, | unsorted, etc. Do you know how we can fix this ? | | | On Wed, Dec 30, 2009 at 7:25 PM, Stéphane Ducasse | <stephane.ducasse@inria.fr | > wrote: | | > Yes lukas now damien was nice to build the images because I could | not do | > them. | > But damien is doing Java daily. | > | | | Of course this is not Damien fault. Everybody here do as much as | possible. | | | | > And you do not like the package browser and we need it :). | > | > So I do not know what to do. | > - first we should add simple trait creation to the OB | > - now frankly I do not know how we could manage moose without | the | > package browser. | > | > | | Yes, most of the problems in a dev image are related usually with the | system | browser :( | | | | > Stef | > | > On Dec 30, 2009, at 7:16 PM, Lukas Renggli wrote: | > | > >> I have already said it several times. Most of the people don't | care how | > >> nice, fast, clean, open source and well programmed is the Pharo | Core | > image | > >> if they cannot use the Dev or Web image. | > > | > > This is what I am telling for years already. I don't know how | other | > > people think about this, but to me it feels very embarrassing to | have | > > to advertise my own way of building images over and over again? | > > | > > Here is it again: I am using the scripts | > > <http://code.google.com/p/pharo/wiki/ImageBuildScripts> to get | from a | > > Pharo 1.0rc1 a fast and stable development and deployment image. | The | > > image loads a well tested and fast OB, a working and well tested | > > refactoring engine, working syntax highlighting, working code | > > completion, and several other tools I use daily and that I cannot | work | > > without. I am not telling it is bug free, but with my personal | > > workflow I can use it without getting interrupted by bugs all the | > > time. And when I encounter a bug, I fix it. | > > | > > I don't think that somebody can build a stable distribution | without | > > using it 12 hours daily. Have a look at PharoCore, it is only | rock | > > solid because Stef is using it all day long to integrate fixes. | Have a | > > look at Squeak Trunk, it only sees improvement because Andreas is | > > using it all day long. Have a look at Debian, Gentoo, ... | > > | > > Lukas | > > | > > -- | > > Lukas Renggli | > > http://www.lukas-renggli.ch | > > | > > _______________________________________________ | > > Pharo-project mailing list | > > Pharo-project@lists.gforge.inria.fr | > > | http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project | > | > | > _______________________________________________ | > Pharo-project mailing list | > Pharo-project@lists.gforge.inria.fr | > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project | > | | _______________________________________________ | Pharo-project mailing list | Pharo-project@lists.gforge.inria.fr | http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project