# Revision history [back]

### Writing portable Sage module

I've been working on a bit of code that is of interest to a bunch of people but far too specific to even be considered for inclusion in Sage. Is it possible to package my code as an spkg, put the binary on a server somewhere, and then have interested parties install it by typing ./sage -t url-to-package? Or should I just stick to distributing my .sage files as tarball?

Sorry if this is already in the developer manual! However, when I checked, most of the instructions dealt with preparing an spkg and submitting it to the trac server, which is not what I want to do.

 2 retagged Kelvin Li 503 ●5 ●12 ●17

### Writing portable Sage module

I've been working on a bit of code that is of interest to a bunch of people but far too specific to even be considered for inclusion in Sage. Is it possible to package my code as an spkg, put the binary on a server somewhere, and then have interested parties install it by typing ./sage -t url-to-package? Or should I just stick to distributing my .sage files as tarball?

Sorry if this is already in the developer manual! However, when I checked, most of the instructions dealt with preparing an spkg and submitting it to the trac server, which is not what I want to do.

 3 retagged Kelvin Li 503 ●5 ●12 ●17

### Writing portable Sage module

I've been working on a bit of code that is of interest to a bunch of people but far too specific to even be considered for inclusion in Sage. Is it possible to package my code as an spkg, put the binary on a server somewhere, and then have interested parties install it by typing ./sage -t url-to-package? Or should I just stick to distributing my .sage files as tarball?

Sorry if this is already in the developer manual! However, when I checked, most of the instructions dealt with preparing an spkg and submitting it to the trac server, which is not what I want to do.