Submitting to SSC and OS-specific files

[Brendan Halpin]

The submission instructions for SSC (http://repec.org/bocode/s/sscsubmit.html) note that a .pkg file is not to be used. Mostly that is not a problem, because SSC creates its own from the package contents.

However, .pkg files also handle OS-specific files (e.g., binary plugins).

The package file specifies a single target here, omamatv3.plugin, and offers 5 OS-specific binaries. The net install command thus knows which one to choose.

g WIN omamatv3.w32.plugin omamatv3.plugin
g WIN64A omamatv3.w64.plugin omamatv3.plugin
g LINUX omamatv3.linux.plugin omamatv3.plugin
g LINUX64 omamatv3.linux64.plugin omamatv3.plugin
g MACINTEL64 omamatv3.mac.plugin omamatv3.plugin
h omamatv3.plugin

How can I make a submission to SSC that specifies which binary to use for which OS?

[Maarten Buis]

For questions like these I would just email Kit and I am sure a solution will be found (and I would not be surprised if one already exists). Kit is a friendly person and this is a legitimate question, so I suspect no problems.

[Sergiy Radyakin]

How can I make a submission to SSC that specifies which binary to use for which OS?

Brendan, congratulations on finishing your plugin and it looks like you've done a great job compiling it for all these different platforms! When submitting to SSC, you just need to describe which plugin file is compiled for which platform. Kit is aware of the platform specificity of Stata plugins, and I had no problems submitting a package containing a platform-specific code. The information you have shown (the pkg file prototype) is sufficient, but expect a few lines to be added (such as minimal Stata version requirement, keywords, etc).

Best, Sergiy Radyakin