Okay. I I have followed you correctly, we have two (mutually incompatible) options :
- (Dima's option) : package curl, pcre and xz as standard packages, and make R depend on them (unconditionnally). - (Jean-Pierre option) : add tjem to Sage's core, but build them if and only if they are not installed systemwide (= useable at Sage's compile time) ; do this before trying to build R. The first option is extremely simple and failsafe. The cost is about 15 MB (sum of all installed files in a temporary "prefix" directory, without shaving anything) and about 3 minutes of compilation time (no parallelism used). We might shave 4,9 MB of docs (local/share/(doc|man). Binaries are about 0.9MB. The total potential cots (sum of sizes of the three build directories) is 89 MB (= potential cost if the three build directories ate kept after building i. e. for debugging purposes). The second one requires hacking the main Sage configuration. I do not feel currently quite at ease with this one, but I'm just reading the relevant docs. I have no idea of the potential costs, save for what can be deduced from the costs of Dima's options. The first option is compatible with the "batteries included" philosophy flaunted by Sage. are the potential 10-15 MB savings worth of hacking the main Sage config file ? Your advice ? -- Emmanuel Charpentier -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
