I think that we should have a group of people controling integration. Stef
> Hello all, > > I just noticed that the December web image (12.2) cannot open context menus > for want of #isMethodNode and #isClassNode. > > When I last built an image, Citezen's installation was pointing to what I am > told is an old copy of RIO which is broken on Windows. apparently this is not pharo's fault. > OS Process did not load cleanly. Bill what we are trying to with metacello is to have configuration of working packages. > Do we have a plan to fix such things? There is an obvious tradeoff between > using the external code in its ideally up-to-date state and having something > that is known to work. Yes Now can you report your problem is a way that we can reproduce them? > At a minimum, we might have a section on the Wiki dedicated to workarounds > for loading packages with problems on Pharo. PackagesTestedInPharo is close; > the Notes column might link to package-specific notes elsewhere on th wiki?? > In some cases (e.g. the context menus), we should probably have needed > methods added to each image as it is built to avoid giving a broken image to > new users. > > Bill > > _______________________________________________ > 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
