Hi Wojciech, On Tue, 2007-05-01 at 14:39 -0400, Wojciech Gryc wrote:
> Finally, I don't mind making a Calc add-in instead. I did notice the > "scaddins" folder and actually toyed with the idea of using that instead. I > just have a few questions about this: The code inside the scaddins module is not external, therefore *does* get distributed with OO.o. So, putting a GPL-code in the scaddins is probably not a good idea in this case. > > 1. How do we expect the user to install this stuff, in general? If I > make a link between C and R, we can't ship it with OO due to licensing > issues, so should we build some sort of built-in installer, or just have a > link somewhere on the OO website? Initially, you could probably put your external R package somewhere on your website, sourceforge etc. that are separate from the OO.o website, then put a URL to it on the Calc page (or something). Later when the licensing issue gets resolved, we can put the code into the main tree. Anyway, we should probably come back to this topic later when we have something to distribute. ;-) > > 2. If I do make an add-in, is there anywhere I can put it in the > source code, or will it be an external package, as discussed in #1? If it > is > an external package, then can I just code a link to R directly in the > add-in? Yes. You'll need to release the package under GPL, of course, but as long as it's an external package, there shouldn't be any licensing issue (that I see). Hope this helps. Kohei -- Kohei Yoshida - OpenOffice.org Engineer - Novell, Inc. <[EMAIL PROTECTED]> --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
