Hi keith I will let lukas answers your questions. And I like this discussion because at the end we should all get a better understanding. I like the idea of an integration build server we all need that.
Lukas can from time to time build too complex software :) (I know he will smile) but he showed with Seaside that he has a sense of code responsibility. So continue to discuss not argue :) Stef On Feb 19, 2009, at 6:11 PM, Keith Hodges wrote: > Lukas Renggli wrote: >>> You are wrong about Sake I think. >>> >> >> I know Sake. I've written a generator for builder.seaside.st. The >> result (or a modified version of it) is included with the Sake >> distribution as Seaside29Builder. >> >> >>> Sake can declare a universe of >>> known-to-work-together packages. Just take a class, declare the sake >>> tasks you know work together in the image you target and things will >>> be as in universe. >>> >> >> Sure, you can use Sake to build something very similar to a Universe. >> However tasks are not declarative, but instead use a script to >> perform >> some actions. In most cases they call Installer to find and load an >> appropriate version (what is already scary in itself). >> > Why? > > They are "mostly" declarative, following feedback from Andreas. If > the > default script is used it simply analyses the url data given, which is > the case for 99% of packages. >> I understand that Package Universe is too restrictive for some cases, >> however I wouldn't dare to replace it with Sake. Sake depends on a >> stack of hacks, it even uses its own compiler to allow uppercase >> method names. > No it doesnt. > > It doesn't depend upon that compiler hack. That hack provides the > ability to put textual data in as an appendix to a method. It is an > entirely independent facility that could be perhaps better included > as a > trait for those that want it. > > I use it when I want to use methods to be a mini database, in the > Mantis > package, and for Bob to be able to manages build scripts in the image > without having to enclose in quotes and escape quotes. >> In the small codebase Code Critics finds 14 serious bugs >> like non existing inst-variable references and message sents that are >> > I don't think it is fair to use code critics as an argument. To me it > appears that you have developed all of these tools for your own use. I > have never even seen you announce their existence to squeak-dev. > Where > is the documentation? >> not implemented anywhere. Of course there is not a single test. > What are you talking about: Sake-Tests. >> The >> way Sake calculates dependencies is totally strange, I am not sure if >> it is even correct. >> > Again, what do you mean? There are two algorithms in use. The first is > lifted directly from rake. The second is stolen directly from > universes. > > Keith > > _______________________________________________ > 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
