On Mon, Feb 20, 2012 at 8:06 AM, Burcin Erocal <bur...@erocal.org> wrote: > Hi Keshav, > > thanks for pointing out this thread. "log messages" is an interesting > title to discuss the future directions for Sage. :) I added > gentoo-science to the CC list, since that is the most likely location > for sage-on-gentoo discussion and the gentoo-developers might be > interested in the contents of this thread. > > On Mon, 20 Feb 2012 22:45:24 +0800 > Keshav Kini <keshav.k...@gmail.com> wrote: > >> Robert Bradshaw <rober...@math.washington.edu> writes: >> > On Fri, Feb 17, 2012 at 1:09 AM, Keshav Kini >> > <keshav.k...@gmail.com> wrote: >> >> Robert Bradshaw <rober...@math.washington.edu> writes: >> >> In the category of "glue code" I meant to include everything in >> >> $SAGE_LOCAL/bin/sage-*. I see much of that stuff as more related to >> >> maintenance of the entire distribution of software we ship than to >> >> the actual Python/Cython code in the Sage library. Of course, if >> >> we do switch to Prefix or something like it, most of it will become >> >> unnecessary, or can actually be fit into the portage data tree as >> >> "Tools", so I see your point. >> > >> > Yeah, tools describes it well (or at least what remains after the >> > package management stuff is gone, like testing and coverage and >> > stuff). >> >> Well, I meant that there is a "Tools" directory in sage-on-gentoo. I'm >> not sure if this is a standard thing in the directory structure of a >> Gentoo Prefix tree, or, if it is, what sort of stuff is supposed to go >> there, but I see some utility scripts, presumably written by François >> or Christopher, in there and was suggesting we might be putting our >> sage-* scripts there too. But I don't know enough about Prefix to be >> sure whether that makes sense. > > AFAIK, Tools contains the scripts that are used to maintain the > overlay. sage-on-gentoo contains these packages for Sage: > > sage-baselayout > sage-clib > sage-data-conway_polynomials > sage-data-elliptic_curves > sage-data-graphs > sage-data-polytopes_db > sage-doc > sage-extcode > sage-flasknotebook > sage-notebook > sage > > baselayout is what gentoo calls basic scripts. That is the package > containing the relevant part of sage-scripts. While I like the > separation of the data packages (I assume these don't depend on code > from the sage library), I am not sure about the clib, doc and the > library separation. I'd like to keep those together to match the Sage > development pattern as close as possible.
Both clib and doc were once separate spkgs. It was painful, and contributions to both were very low (and rarely did a change to clib not require a parallel change to the library). IMHO, there's no reason for extcode to be its own package either--I can't think of a single time I have modified extcode without modifying (usually extending) the sage library. Of course I've been advocating putting "baselayout" into this common repository as well. On the nix front, I love the ideas, but have never actually used it myself so have no idea about it's maturity (whereas sage-on-gentoo obviously works). - Robert -- 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
