Article View: gnu.gcc.help
Article #42697A question on legacy matters on LIBS
From: John Eaton
Date: Thu, 09 Nov 1995 00:00
Date: Thu, 09 Nov 1995 00:00
52 lines
3022 bytes
3022 bytes
Mirsad Todorovac <tm@rasips2.rasip.etf.hr> wrote: : 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 isn't a newsgroup, but there is a mailing list, help-octave@bevo.che.wisc.edu. : 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. This may be a problem, but I'm not sure what to do about it other than installing a README file for every installed library. Even then, people who use the libraries may not see the file. I think it is reasonable to assume that they will have at least taken a quick look at the documentation, where they should find terms for redistribution. If you're going to redistribute something, I would expect you to at least try to find out what the license/copyright terms are. : 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 . No, I think it is intentional. As I see it, the purpose of distributing packages like Octave is not to save time for people who are not willing to share. There's nothing that says that just because something is in the form of a library that it has to be covered by the LGPL. If you don't like the terms under which these programs are distributed, then you don't have to use them. Followups to gnu.misc.discuss. jwe
Technical Details
Message-ID:
<199511091750.LAA05515@bevo.che.wisc.edu>Path:
arc1-ca.pugleaf.net!unknown!not-for-mailReferences:
<46omms$sv1@bagan.srce.hr>Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 11318c,149e4152d6edb071 X-Google-Attributes: gid11318c,public From: jwe@bevo.che.wisc.edu (John Eaton) Subject: A question on legacy matters on LIBS Date: 1995/11/09 Message-ID: <199511091750.LAA05515@bevo.che.wisc.edu> X-Deja-AN: 119014268 distribution: gnu sender: daemon@cis.ohio-state.edu references: <46omms$sv1@bagan.srce.hr> organization: GNUs Not Usenet followup-to: gnu.misc.discuss newsgroups: gnu.gcc.help