guile-core and readline

[Roland Orre <orre@nada.kth.se>]

I have two suggestions to discuss here concerning:
1) What the libguile catalogue should contain.
2) Readline default strategies.

1) The libguile catalogue under guile-core should only include what
is necessary to create the libguile, i.e. what is contained in the
LGPL library "libguile.so". The executable program "guile", which is
to be seen as a GPL application using the libguile library should have
a separate catalogue under "guile-core", e.g "guile-command" or just
"guile".

2) The readline should not be part of libguile as it is (was), it
should have another separate catalogue under guile-core e.g 
"libguile-readline". In the "guile-command" directory should
the guile command be linked together with the libguile library
and the libguile-readline library.

Readline should be enabled by default in the command line guile.
This is a good PR for newcomers and makes it much easier for
anyone to start using guile.

As I understand this would give no licence problems with readline
when guile is used as a command and readline will then by default not
be included in an application.

A further restriction would be to have readline under the guile-command
catalogue only. Then it would be slightly harder to get it illegally
included in a (commercial) application, but will then affect also other
GPL applications where guile may be included. Each of these applications
then have to include the readline module during linking.

If the readline is not included by default in the command line guile
then there will occur other problems when patches would have to be
applied to every distribution or "snapshot" to get guile work as you
want.

/Roland Orre