Hi Camm,
I think the runtime cannot distinguish between libraries because it is the library that
gcl is linked with that is loaded. You can also compile gcl with build dependency
libeditreadline-dev if you remove the RL_READLINE_VERSION check that is introduced with
patch Version_2_6_13pre12. Additionally you could remove "READLINE" from the GPL banner
then (not necessary).
I see that you are also the gcl maintainer, so you can coordinate uploads of maxima and
gcl linked with libedit.
Thanks,
Bastian
Am 12.10.21 um 16:07 schrieb Camm Maguire:
Greetings, and thanks for this!
It would be nice to migrate to editreadline. GCL at present constructs
a binary license banner indicating GPL'ed components. How would runtime
gcl distinguish between these two libraries of the same name?
Take care,
Bastian Germann <bastiangerm...@fishpost.de> writes:
Control: found -1 5.44.0-3
On Sat, 2 Jan 2021 18:48:19 +0100 Bastian Germann <bastiangerm...@fishpost.de>
wrote:
However, that is orphaned in Debian, so libeditreadline-dev should
be preferred, which does not compile with your package without any
patch. It links with the BSD-licensed libedit library which is a
readline replacement.
The current version compiles with libeditreadline-dev without any patch.
I do not see the build influenced by it and guess libreadline is still loaded
via gcl.
Can you please comment on this?