You know someone (me). If the installation is not a moving target, then I can add it to the list of things I do to create a new image, but having Seaside in place has been appreciated. In general, "that's xyz's problem" wears thin. Taken to extremes, it could turn into "sure, the browser is broken, but that's not Pharo's doing; the debugger trashes the image sometimes, but that's the external debugger package that's to blame; you can't build stable web applications, but that's not Pharo's problem, ..." True as some claims of this type might be, we won't be able to get away with it forever, and we should have things that are known to work or look for ways to replace them.
Bill ________________________________ From: pharo-project-boun...@lists.gforge.inria.fr [mailto:pharo-project-boun...@lists.gforge.inria.fr] On Behalf Of Mariano Martinez Peck Sent: Tuesday, January 05, 2010 8:37 AM To: Pharo-project@lists.gforge.inria.fr Subject: Re: [Pharo-project] What about killing PharoWeb images? 2010/1/5 Schwab,Wilhelm K <bsch...@anest.ufl.edu<mailto:bsch...@anest.ufl.edu>> My big concern is that either testing of Pharo will suffer (things that are made difficult tend not to happen), or that a bunch of us will end up with ad-hoc build processes rather than having it done in one place with a chance of getting it right. I don't think so. How many people do you think that are using PharoWeb? I even don't know anyone. And we have enough beta testers for Dev images. And the difference between Dev and Web images is that in Web there are also the seaside packages, but there is NO change in the packages load. So, the only issues that can appear in PharoWeb but not in PharoDev are those related to Seaside, and that's seaside, not us. It would be cool to hear also the opinion of the pople who is using pharoweb images (if there is anyone). Cheers Mariano Bill ________________________________ From: pharo-project-boun...@lists.gforge.inria.fr<mailto:pharo-project-boun...@lists.gforge.inria.fr> [mailto:pharo-project-boun...@lists.gforge.inria.fr<mailto:pharo-project-boun...@lists.gforge.inria.fr>] On Behalf Of Mariano Martinez Peck Sent: Tuesday, January 05, 2010 5:02 AM To: Pharo-project@lists.gforge.inria.fr<mailto:Pharo-project@lists.gforge.inria.fr> Subject: Re: [Pharo-project] What about killing PharoWeb images? On Tue, Jan 5, 2010 at 12:34 AM, Adrian Kuhn <ak...@iam.unibe.ch<mailto:ak...@iam.unibe.ch>> wrote: Lukas Renggli <reng...@...> writes: > If you are really into building images, you should build them for YOU > and not for anybody else. Otherwise, I think, they are never going to > fly. +1 But the concern about this emails was final users, maybe even beginners and new comers. Most of us (who have some time with Pharo) use our own build images, but they do not. --AA _______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr<mailto: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<mailto: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
