Follow-up Comment #8, task #16666 (group administration):

> This is right, and we are on a higher level now---what year and what name
> should be listed?

According to
[https://www.gnu.org/prep/maintain/html_node/Copyright-Notices.html]:
"Copyright (C) year1, year2, year3 copyright-holder"

Notice the capital C, I had a lowercase c. Done.

I checked every file to see which year I updated them, and added those year
numbers. Done

And for the copyright-holder, the gnu link says "you should know who is the
copyright holder for your package.". So it must be me, and Nicolas Dato is my
name. If "Dato" is confusing, Dato is my real surname. In spanish it means
"data" and that's just a coincidence. It happens from time to time that
someone thinks I'm saying "data" like "here is my data: Nicolas" and I have to
explain that that's my surname.
I didn't copy source code from anywhere. I didn't use any LLM neither.
If I am violating someone else's copyright please let me know, I don't want to
do that.

> One posibility I can see is that the developers distribute the package under
> the GPLv2 and allow other people use it under later versions; but one should
> ask the developers to be sure.

Just to be clear, I'm not distributing valgrind. If it is found already
installed in the system, then make check uses valgrind.

However, I think valgrind works by linking the program to valgrind's own
libraries. I know this is an important topic in the GPL and one reason for the
LGPL, isn't it?
How does this affect running a test with valgrind if valgrind is already
installed? Can we use valgrind to run a test that has the Expat license? Is
that legal?

Now, out of topic, but as we are talking about this. Can we use valgrind
against a proprietary software?

> The point is, if people combine software under these licenses, then the GPL
> is what they have to follow.

Thanks for all the explanation, it's good to know!

You can still use the same link to download the tar.

Regards.


    _______________________________________________________

Reply to this item at:

  <https://savannah.nongnu.org/task/?16666>

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

Attachment: signature.asc
Description: PGP signature

Reply via email to