I think I can rewrite the gap code in Sage now. However, it would be a rather large patch (read "patch bomb") though.I could also just delete it and the method in the class which uses it.
On Fri, Dec 5, 2008 at 5:54 AM, mabshoff <[EMAIL PROTECTED]> wrote: > > Hello folks, > > the extcode repo in Sage is somewhat of a dumping ground what doesn't > really fit anywhere else. Below is the disk use of all directories > that aren't more or less empty: > > 44K dist > 36K gap > 24K images > 1.2M javascript > 228K magma > 52K maxima > 3.0M notebook > 1.9M pari > 400K pickle_jar > 204K sagebuild > 16K singular > 7.2M total > > The 3.0 MB notebook is at least size-wise 95% javascript, too. We > (Jason Grout is doing all the hard work) are in the process of moving > all the javascript packages we use (jsmath, jquery, ...) to spkgs so > that the repo will be much smaller in the future while the .hg repo > information itself will grow by another couple MB. In the end the > compressed extcode.spkg will be just as large as before the removal. > And shipping such an amount of basically 3rd party code we checked in > and then removed seems like a waste of resources. But what to do? > > (a) nuke the extrepo and move things into other places. The > pickle_jar could go into the main Sage repo, the pari scripts into the > pari.spkg, the images and the notebook code could also be part of the > main repo. That leaves certain code for Maxima, Singular and Magma in > search of a place to hang out. > > (b) reset the extrepo. This is the less invasive option, but would > destroy the version history of some of the files. One option here is > to check in files in the name of the previous main author, but it > seems like a bad move. > > Either way we should do something about the extocde repo. Since the > doc repo will die in 3.3. it seems like an excellent opportunity to > finish some long needed cleanup. I could certainly imagine some > combination of (a) and (b), i.e. the pari data seems to be large > untouched in a while and the pari.spkg would seem like a canonical > place for it. Putting those pari scripts and data under revision > control also seems rather pointless. > > Thoughts? > > Cheers, > > Michael > > > --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
