Follow-up Comment #10, task #16666 (group administration):
> It depends on how understand 'linking'; what matters for the GPL is whether
> the program makes a combined work with valgrind.
> And it doesn't, like it doesn't make a combined work with a debugger or with
> the kernel of the operating system. It's more like running the program in an
> interpreter.
Oh! I see! Thanks.
>> Do you realize what files are copyrightable?
>
> I think I didn't realize that Makefile code is copyrightable too. And any
> file with more than 10 lines.
Now I found tuberia.pc.in which was more than 10 lines. I added the copyright
notice to it.
> For example, you did copy INSTALL from somewhere, didn't you?
Yes, I don't remember where I copied it from, or how I generated it. But I
know I didn't write it.
So I wanted to check if I modified it somehow so I tried to remember about
that INSTALL file.
I read that automake can generate the INSTALL file if it isn't found. However,
I couldn't do it now.
So I searched and I found that the automake package installed in my PC has a
file in /usr/share/automake-1.16/INSTALL that the same as the INSTALL file I
have.
I don't know if I generated the file running any autotool software, or if I
found the file in /usr/share and copied it.
I can't find the issue with it. I didn't modify it, so I can't claim copyright
over it, and neither add another year number because I didn't modify it.
Then is the legal notice, which is simple, concise, and the only requirement
is to preserve the copyright and "this notice".
So I'm at odds here. What am I missing? Should I add my name along side the
FSF because I'm distributing it?
Regards.
_______________________________________________________
Reply to this item at:
<https://savannah.nongnu.org/task/?16666>
_______________________________________________
Message sent via Savannah
https://savannah.nongnu.org/
signature.asc
Description: PGP signature
