octave: make distributable

[Joshua Root]

On 2016-12-23 07:25 , Marcus Calhoun-Lopez wrote:
> As octave takes quite a while to build, I would like to make it distributable.
> I have a patch that I believe will allow this to happen.
> However, both licenses and the buildbots are bewildering to me.
>
> May I request feedback as to whether this is both correct and legal?
>
> Thank you,
> Marcus
>
> 1) Add
>     configure.args-append --without-openssl
>
> 2) Add the following code:
>     # octave does not depend directly on openssl, but it
>     #    is brought in by many of the other dependencies
>     #
>     # openssl's libraries are never linked into octave
>     # openssl's header files are never included
>     # the openssl part of Qt is never used
>     #
>     # similarly for libpaper
>     #
>     license_noconflict  \
>         openssl         \
>         libpaper

If openssl is indeed not loaded into the executable at runtime then that 
is fine. But if it uses anything that even indirectly uses something 
else that uses openssl, thus causing it to be loaded, then at least the 
FSF's position is that it is a derivative work. (Other organisations' 
lawyers may disagree, but I mention FSF because their position is one of 
the more restrictive and thus safer for us to follow.)

- Josh