I should have posted this question here instead of at #6865, as the answer is probably interesting to many people here. I'd heard things about MANIFEST.in, but for some reason didn't have a clear idea of what it was or what I should do about it. It would be nice if something was added to the developer's guide...
> What is devel/sage/MANIFEST.in and when do we need to add things to it? (answer by mpatel) I believe the sage -bdist and sage -sdist invoke distutils to build sage-*.spkg. Distutils uses SAGE_ROOT/devel/sage/MANIFEST.in to determine which files to include in the distribution. If we add files to the local Mercurial repository, we should check that some line(s) in MANIFEST.in includes the newly tracked files or add a new line. Otherwise, the next (pre-)release of Sage will not include them. As mvngu puts it, this results in repository corruption. Previous sightings: #4460, #5653, #5799, #6568, etc. Jason -- Jason Grout --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
