> Well, there's a technical and legal question here. On a technical note, it's > better to put the C files in an spkg and then link to them from the Sage > library rather than check external code into the Sage library itself. (If > you want help making an spkg, I'd be happy to do that.)
Hmmmm ^^; Even if we are talking about 3 small C files (and actually 2, as one of them only contains examples) ? I can make a spkg if needed, but I thought we could forget it in this case.. These C files are not likely to be updated, by the way. I also tried to make this clear by creating a src/ directory inside of modular_decomposition/ containing only these files, and the LICENSE file. Nathann -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
