On Mon, 2022-02-21 at 09:24 +0100, Francesco Pretto wrote:
> if I want to make turn a tool into an API, for the benefit of
> everybody, I can not because that would be move GPL into LGPL which
> is license incompatible (the other way is fine).
Hi,
I see, thanks for the clarification. I agree it makes sense to relax
the licenses on the tools too, if the licenses will be changed in the
future. Extracting the tools into a separate project won't change
anything on the arguments you provided. For a simplicity of the project
maintenance it still makes sense to keep them together, from my point
of view.
You mentioned that you cannot properly test the tools, that it's one of
the (other) reasons you'd like to split the tools out of the project. I
do not ask you to maintain the tools, especially their functionality,
the unit tests are there to test the PoDoFo code. If the tools have
bugs, then the tools can be fixed. That's fine. Knowing that the tools
can be compiled when the core library API changes is an essential
thing, which can be achieved for free, just by keeping them in the same
code base.
> But documentation is often licensed in different terms because
> source code license terms mostly don't apply with the nature of
> documentation.
Yeah, that was my main point, a little hidden in the paragraph. There
are cases where different parts cannot use the same license.
Bye,
zyx
_______________________________________________
Podofo-users mailing list
Podofo-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/podofo-users
