Follow-up Comment #45, task #16584 (group administration):
> The GPL has a section for the copyright holders after the end of terms
> and conditions, "How to Apply These Terms to Your New Programs".
> Since other parts are written for the recipient do you refer to that
> section when you say 'guidance'? But then the LGPL contains no such
> section. Do you mean something else?
I noticed the LGPL doesn't have a guidance for applying LGPL to a new program.
But, in the LGPL there are:
2. Conveying Modified Versions.
3. Object Code Incorporating Material from Library Header Files.
b) Accompany the object code with a copy of the GNU GPL and this license
document.
4. Combined Works.
5. Combined Libraries.
However they are under specific conditions, maybe I can not use them as
guidance.
I am sorry, at this point, I really don't know whether I as a copyright holder
who firstly whats to distribute StoneValley library under LGPL license, should
add a copy of both GPL and LGPL to my project or not, because I can't find a
reference. Could you give me some hints?
> This isn't just about having to find a copy fo the LGPL somewhere.
> When the tarball contains no copy of the LGPL, the user can't tell
> if it's because the distributor forgot to include it or because
> the package was really relicensed, for instance, under the GPL.
Thank you. Now I understood.
> > > Good; but I'd like to know how you get the list of the candidate files
> > > to check in the first place.
> > I choose those program files whose line numbers greater than 10 to add
legal
> > notices:
> The question is, how you find those files.
To be honest, I actually just mimic what the GLIBC redistributors does and
revise my files. So, copyright notices only appear at every .c and .h file.
> > I think copyright notice is:
> > Copyright (C) <year> <full name>
> > It consists of a word Copyright, a copyright sign '(C)', the year or a
range
> > of years copyright takes in charge and the copyright holder's full name.
>
> Magnificent. Now we can see two points.
>
> Copyright notices don't specify the distribution terms of the package.
> README in file #56448 includes no copyright notice.
>
> Can you see that?
Yes, I can see them. I altered my tarball again. Please evaluate it.
I altered
./README file at line 10.
./NOTICE file at the top.
./Examples/README at the top.
I am sorry to bother you to evaluate. You have patiently talked with me a lot.
No need to repeat that I need your help till I finish submission.
Salute
(file #56548)
_______________________________________________________
Additional Item Attachment:
File name: StoneValley.tar Size: 870KiB
<https://file.savannah.nongnu.org/file/StoneValley.tar?file_id=56548>
AGPL NOTICE
These attachments are served by Savane. You can download the corresponding
source code of Savane at
https://git.savannah.nongnu.org/cgit/administration/savane.git/snapshot/savane-f3f59ac28bc0bce1dfd9d85df4a8c783e526ec17.tar.gz
_______________________________________________________
Reply to this item at:
<https://savannah.nongnu.org/task/?16584>
_______________________________________________
Message sent via Savannah
https://savannah.nongnu.org/
signature.asc
Description: PGP signature
