8. Producing New Sage Packages

If you are producing code to add new functionality to Sage, you might consider turning it into a package (an spkg file) instead of a patch file. If your code is very large (for instance) and should be offered as an optional download, a package is the right choice; similarly, if your code depends on some other optional component of Sage, you should produce a package.

If you're not sure whether to build an spkg file or a patch file, ask for advice on sage-devel.



Subsections
See About this document... for information on suggesting changes.