🚀 go-pugleaf

Hello,

Actually, I'm currently installing octave-1.1.1.  So this is not a valid gcc
help question, therefore I apologize (I was not able to find newsgroup
discussing octave).

There are some libs distributed with octave, as well as with many other
GNU packages.  Somebody might just find this libs usefull, and time-saving
in developing other projects.  So, let's go to the main question:

1) octave-1.1.1 installing procedure installs such libs at widely accesable
   directories, like /usr/local/lib.

2) there is no COPYING.LIBS clause in octave distribution, but the COPYING
   one.  This means that if anybody uses such libs e.g. libcruft.a, they
   MUST provide whole of their other source files with their distribution.
   Notice that it's not neccessary that they ever see the actual source of
   the lib, and they may not distribute it with the package they develop.
   They may expect it to be on the end users' system.

3) Why e.g. readline.a is not covered by COPYING.LIBS, which is far less
   demanding than COPYING.  It may be smart to allow programmers who want
   to freelly distribute derived programs they write, but not their source code
   (because they cannot convince their management etc.) to have right to
   use such crufty libs under COPYING.LIBS clause.

4) Perhabs it is done by error (readline.a is taken from bash probably),
   maybe it should say COPYING.LIBS, as for libg++.a .

--------- Thanks for your patience -- Mirsad


--
Mirsad Todorovac at Electrical Engineering Faculty, University Zagreb, Croatia
mirsad.todorovac@etf.hr, tm@rasip.etf.hr