Sys Req, Solaris and Seasonal about x13binary

[eddelbuettel]

All good points. Let's make sure we get a Solaris binary---or maybe even a process.

Here is an idea: We could just use the 'residual' case (ie not Windows but Unix, and neither Linux nor Darwin/OS X) and then download the source tarball---which we'd add to the x13prebuilt repo---and build. If we fail, we state the error; if we succeed we have generalized the method.

I can spec on Linux just overriding the default.

The condition/override is still a good idea. If the user has set, say, an options("x13.override.check") to TRUE, and/or set env.var., then we skip the initialization. We could also use a pre-existing value of X13PATH for this (though it may have transition problems for existing users).

And then we could nix the SysReq again which would be cleaner.

[christophsax]

The changes in seasonal are quite small. If you continue to specify X13_PATH, you will use your own binary, independent of the OS (but you will get a message if you are not on Solaris). On Solaris, you have to specify X13_PATH, as in previous versions of seasonal.

That way, existing users will experience almost no changes when updating, except of a new startup message. To get the fun of x13binary, they have to remove their manual specification of X13_PATH first.

[eddelbuettel]

Nicely done. I had seen your previous if/else testing for the env var.

[eddelbuettel]

So we can close this, I guess?