savannah-register-public
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[task #16584] Submission of StoneValley


From: Ineiev
Subject: [task #16584] Submission of StoneValley
Date: Tue, 8 Oct 2024 12:38:55 -0400 (EDT)

Follow-up Comment #36, task #16584 (group administration):


> > Let us see where that passage mentions the LGPL.
> 
> > The LGPL is definitely not "copyright notice".
> > The LGPL isn't a notice stating that "this License" (that is, the GPL)
> applies to the code.
> > The LGPL has nothing to do with "any non-permissive" terms because > it's
a
> set of permissions.
> > The LGPL isn't a notice of absense of any warranty, those notices come in
> the text of the GPL.
> > "This License" in the context of the GPL means the GPL.
> 
> > Do I miss anything?
> 
> There is a block of text at the tail of GPL license to show users how to
apply
> LGPL:
> 
> The GNU General Public License does not permit incorporating your program
into
> proprietary programs. If your program is a subroutine library, you may
> consider it more useful to permit linking proprietary applications with the
> library. If this is what you want to do, use the GNU Lesser General Public
> License instead of this License. But first, please read
> <https://www.gnu.org/licenses/why-not-lgpl.html>.

You are right, the GPL includes that passage; however, it speaks
about the LGPL as about a completely different license, and it's
written after the end of terms and conditions.

I think you can't find any provisions requiring that a copy
of the LGPL be included in a source tarball because it's a set
of additional permissions, and GPLv3 Section 7 explicitly says,
"[w]hen you convey a copy of a covered work, you may at your option
remove any additional permissions from that copy."

What do you think?

> You sent me the link mentioned these following 2 types of  copyrightable
> files:
> 
> a) For copyright purpose, any file more than ten lines long is nontrivial,
so
> it should have copyright and license notices.
> 
> b) If some of your files cannot carry such notices (e.g. binary files), then
> you can add a README file in the same directory containing the copyright and
> license notices.

Excellent.  Have you added copyright and license notices to every
such file in your tarball?



    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/task/?16584>

_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/

Attachment: signature.asc
Description: PGP signature


reply via email to

[Prev in Thread] Current Thread [Next in Thread]