G
Guest
Thanks! I see I was wrongly/under informed here... I hadn't intended
to start a discussion about ideologies.
My interest is in the context of a project centred on a closed-source
core which needs to be extended to allow scripting of its abilities. I
can envision freely shared embedded scripts - but this is not an
option for the existing project core. Ruby looks as if it would be a
great language to embed from a technical perspective, but (as this is
one of several potential approaches) I want to be sure that using Ruby
in this way would not be prohibited (or frowned upon by the ruby
community.)
If Ruby were to be used, the standard ruby distribution would need to
be shipped, there would be a number of sample 'fragments' of Ruby
source code (public domain licence here would be ideal) and a simple
library of 'helpful' ruby classes likely to be useful to people
extending the closed system with their own bespoke scripts. There
would also need to be several proprietary 'server' executables into
which a Ruby interpreter has been embedded. These would definitely not
comply with the GPL as not all the source code can be shipped for these
executables.
(I think) you've confirmed that Ruby should not pose a licence
problem in this context. I'll have to carefully read the licence of
the distribution before any decision is made.
Thanks again,
Steve
to start a discussion about ideologies.
My interest is in the context of a project centred on a closed-source
core which needs to be extended to allow scripting of its abilities. I
can envision freely shared embedded scripts - but this is not an
option for the existing project core. Ruby looks as if it would be a
great language to embed from a technical perspective, but (as this is
one of several potential approaches) I want to be sure that using Ruby
in this way would not be prohibited (or frowned upon by the ruby
community.)
If Ruby were to be used, the standard ruby distribution would need to
be shipped, there would be a number of sample 'fragments' of Ruby
source code (public domain licence here would be ideal) and a simple
library of 'helpful' ruby classes likely to be useful to people
extending the closed system with their own bespoke scripts. There
would also need to be several proprietary 'server' executables into
which a Ruby interpreter has been embedded. These would definitely not
comply with the GPL as not all the source code can be shipped for these
executables.
(I think) you've confirmed that Ruby should not pose a licence
problem in this context. I'll have to carefully read the licence of
the distribution before any decision is made.
Thanks again,
Steve