2011/3/9 Harald Schilly <[email protected]>: I understand that this kind of post, besides attempting to state it is a friendly one, could cause more harm than good. The TV show probably would have a small specialized audience :-) But the rants/discussions, and ego wars (not so much as in some other projects) that happens from time to time should be worth a watch.
> exactly how did you come up with 280 points? Not "exact" values, as I just did a quick read and add to a sum, but, considering sage base code and mandatory spks, the biggest values I considered were: Building from source - with your own build tool for this code [ +100 points of FAIL ] (( spk-* shell scripts )) Bundling - Your source only comes with other code projects that it depends on [ +20 points of FAIL ] - If your source code cannot be built without first building the bundled code bits [ +10 points of FAIL ] - If you have modified those other bundled code bits [ +40 points of FAIL ] Libraries - Your source does not try to use system libraries if present [ +20 points of FAIL ] But I did not account: Releases - Your releases are only in an encapsulation format that you invented. [ +100 points of FAIL ] (( spkgs )) > quoting to box on top: > """There are obvious exceptions, such as the Linux kernel. Generally these > exceptions work because they started out small and the community and code > grew together. """ > Therefore I'm glad Sage started <17mb and grew slowly: > http://sagemath.org/src-old/ > > Besides that, your first two points are exactly the reasons why Sage needs > this kind of isolation because there is no way to adopt to all variations of > versions distributions are equipped with while still focusing on regular > releases and maintaining quality. Yes. That mainly because sage is not considered a core package. Still, the Mandriva rpm should be "good enough" as the crashes at exit happens only in around 3-5% of the doctests, and weirdly, if cut&pasting the test cases, and trying to bisect the problem, it goes away, so, it should be some issue when a very large amount of objects are allocated. With valgrind, unless using something like --free-fill=0x51, otherwise, it fills released memory with zero, and the double free problem "goes away". > H Paulo -- To post to this group, send an email to [email protected] To unsubscribe from this group, send an email to [email protected] For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
