[Diritto] Compupic linkato staticamente?
Alceste Scalas
tjoad@gmx.it
Tue, 25 Sep 2001 01:17:57 +0200
--u3/rZRmxL6MmkK24
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Mon, Sep 24, 2001 at 05:17:41PM +0200, Simo Sorce wrote:
> "Roberto A. F." wrote:
> > Davide Bolcioni wrote:
> > > Ho appena guardato la pagina [di CompuPic] e non ci posso
> > > credere: affermano che =E8 linkato staticamente.
> >=20
> > Si pareva anche a me... infatti prima d'ora non aveva mai subito traumi
> > dovuti al cambio di librerie
> > Il link statico dovrebbe essere una violazione della GPL per un
> > programma come questo... o no?
>=20
> Solo se le librerie sono sotto licenza GPL, se sono sotto licenza
> LGPL invece e' ok, e' proprio il motivo per cui e' stata fatta la LGPL.
Premessa: innanzi tutto, bisognerebbe vedere _cosa_ sia
effettivamente linkato staticamente in CompuPic (secondo me,
soltanto le librerie grafiche, e non le glibc).
In ogni caso, non sono un profondo conoscitore della GNU LGPL, ma la
situazione dovrebbe essere piu` complessa...
Ovvero, se CompuPic utilizza le glibc (o qualunque altra libreria
GNU LGPL'ed), allora e` nececessario che:
(a) l'eseguibile finale utilizzi le glibc tramite dynamic linking;
(b) oppure, se viene utilizzato il linking statico, allora si devono
fornire almeno i file .o di CompuPic, che permettano all'utente
p. es. il re-linking di tutto il programma con una versione
modificata delle glibc. E occorre rendere disponibili anche i
sorgenti delle glibc, con le eventuali modifiche apportate per
creare l'eseguibile closed-source distribuito al pubblico.
Non ho mai utilizzato CompuPic, ma mi stupirei se un programma cosi`
diffuso non rispettasse uno dei due punti qui sopra... Qualcuno ne
sa di piu`?
Incollo di seguito la sezione della GNU LGPL a cui ho fatto
riferimento.
Ciao,
Alceste, che di GNU LGPL ne capisce quanto di idrogrammatologia
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
6. As an exception to the Sections above, you may also combine or
link a "work that uses the Library" with the Library to produce a
work containing portions of the Library, and distribute that work
under terms of your choice, provided that the terms permit
modification of the work for the customer's own use and reverse
engineering for debugging such modifications.
You must give prominent notice with each copy of the work that the
Library is used in it and that the Library and its use are covered
by this License. You must supply a copy of this License. If the
work during execution displays copyright notices, you must include
the copyright notice for the Library among them, as well as a
reference directing the user to the copy of this License. Also, you
must do one of these things:
a) Accompany the work with the complete corresponding
machine-readable source code for the Library including whatever
changes were used in the work (which must be distributed under
Sections 1 and 2 above); and, if the work is an executable
linked with the Library, with the complete machine-readable
"work that uses the Library", as object code and/or source code,
so that the user can modify the Library and then relink to
produce a modified executable containing the modified Library.
(It is understood that the user who changes the contents of
definitions files in the Library will not necessarily be able to
recompile the application to use the modified definitions.)
b) Use a suitable shared library mechanism for linking with the
Library. A suitable mechanism is one that (1) uses at run time
a copy of the library already present on the user's computer
system, rather than copying library functions into the
executable, and (2) will operate properly with a modified
version of the library, if the user installs one, as long as the
modified version is interface-compatible with the version that
the work was made with.
c) Accompany the work with a written offer, valid for at least
three years, to give the same user the materials specified in
Subsection 6a, above, for a charge no more than the cost of
performing this distribution.
d) If distribution of the work is made by offering access to
copy from a designated place, offer equivalent access to copy
the above specified materials from the same place.
e) Verify that the user has already received a copy of these
materials or that you have already sent this user a copy.
For an executable, the required form of the "work that uses the
Library" must include any data and utility programs needed for
reproducing the executable from it. However, as a special
exception, the materials to be distributed need not include anything
that is normally distributed (in either source or binary form) with
the major components (compiler, kernel, and so on) of the operating
system on which the executable runs, unless that component itself
accompanies the executable.
It may happen that this requirement contradicts the license
restrictions of other proprietary libraries that do not normally
accompany the operating system. Such a contradiction means you
cannot use both them and the Library together in an executable that
you distribute.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
--=20
This .signature is free software; you can redistribute it and/or modify it
under the terms of the GNU General Public License as published by the Free
Software Foundation; either version 2 of the License, or (at your option)
any later version. ___________________________________=
=20
______________________________________) PGP information in e-mail header |
--u3/rZRmxL6MmkK24
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE7r78lKdo6EofyCO4RAr41AJ480LE5RGwYw4OWrLpnm4qHGEbiZACgs6qY
jsCvsi3kpmSwa6RSzBwnVqY=
=ZDzL
-----END PGP SIGNATURE-----
--u3/rZRmxL6MmkK24--