Follow-up Comment #9, task #16596 (group administration): On Sat, Nov 09, 2024 at 06:01:46AM -0500, simphone wrote: > Follow-up Comment #8, task #16596 (group administration): > > Upgraded openssl to version 3.0, which uses the apache license. Here's the > updated tarball: > > http://www.simphone.org/0.9.3/simphone-src-0.9.3-a2.tar.gz
This URL serves me with a HTML page depending on proprietary JavaScript.
> We care for reprodicibility on all platforms Simphone can run on.
...
> On Mac OS X, Xcode 3.2.6 is to be installed. On
> GNU/Linux, one has to start by installing an ISO image of Debian GNU/Linux
> 6.0.10; in that case, the whole OS is defined as "tools and libraries" for
> the
> purpose of binary reproduction.
If you require to install a specific image of an OS in order to reproduce, you
could as well require to install specific versions of MinGW and other tools
like a shell on that platform instead of distributing the generated files the
users have to rely on; if it were acceptable to you, that would resolve the
issue of the absense of valid legal notices in those files.
>> As far as I understand, RPSL section 4.2 allows to link to the works under a
>> set of licenses, but it says nothing about whether those licenses allow
>> linking with code under RPSL. On www.gnu.org, it is listed as
>> GPL-incompatible,
>
> Sorry to bring this up again; after rereading I'm not really sure what you
> mean by "linking". So I want to point out that Simphone binaries never did
> contain any RPSL-licensed code. The latter was only called by the build
> scripts (at compile time) in order to bring the binary size down, by removing
> unused machine code. Does that change anything? If so, we would be glad if we
> could re-add rlink; else we keep it removed as already agreed and done.
By linking I mean making a single combined work.
We were discussing this in the context of RPSL-licensed code included in your
tarball, so effectively it was a part of your package, and in order to comply
with Savannah hosting requirements it needed to be GPL-compatible.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/task/?16596>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
signature.asc
Description: PGP signature
