From: Mark Wielaard <mark@klomp.org>
To: Florian Weimer <fweimer@redhat.com>
Cc: psmith@gnu.org, Guinevere Larsen <guinevere@redhat.com>,
"gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: Improve GDB's first user experience by reducing "print_gdb_version" output
Date: Fri, 30 May 2025 22:39:01 +0200 [thread overview]
Message-ID: <20250530203901.GC15893@gnu.wildebeest.org> (raw)
In-Reply-To: <877c1yjqcj.fsf@oldenburg.str.redhat.com>
Hi,
On Fri, May 30, 2025 at 01:22:04PM +0200, Florian Weimer wrote:
> * Mark Wielaard:
> >> I had remembered that interactive programs should generate copyright
> >> information at startup, but the most I can find in the current GNU
> >> Maintainer's manual is
> >
> > The GPL itself contains the recommendation at the end (after the
> > actual terms and conditions) in the section "How to Apply These Terms
> > to Your New Programs". It is even shorter than Guinevere's suggestion,
> > it recommends outputting just 4 lines:
>
> It also contains a rule that if the notice is present, you must not
> remove it and distribute the result:
It does define the "Appropriate Legal Notices" as the copyright, no
warrenty notice and how to view the license. And they can be collapsed
into one menu/command/option item if a list of them is presented.
> | An interactive user interface displays "Appropriate Legal Notices"
> | to the extent that it includes a convenient and prominently visible
> | feature that (1) displays an appropriate copyright notice, and (2)
> | tells the user that there is no warranty for the work (except to the
> | extent that warranties are provided), that licensees may convey the
> | work under this License, and how to view a copy of this License. If
> | the interface presents a list of user commands or options, such as a
> | menu, a prominent item in the list meets this criterion.
>
> | d) If the work has interactive user interfaces, each must display
> | Appropriate Legal Notices; however, if the Program has interactive
> | interfaces that do not display Appropriate Legal Notices, your
> | work need not make them do so.
>
> I don't know what the rules are for removing it upstream.
I don't think there are different rules for up or downstream. You only
have to preserve those lines of the notice that fall under the
"Appropriate Legal Notices".
Cheers,
Mark
next prev parent reply other threads:[~2025-05-30 20:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-27 20:43 Guinevere Larsen via Gdb
2025-05-27 21:38 ` Paul Smith via Gdb
2025-05-28 7:33 ` Phi Debian via Gdb
2025-05-28 12:19 ` Eli Zaretskii via Gdb
2025-05-28 12:24 ` Guinevere Larsen via Gdb
2025-05-28 13:04 ` Paul Smith via Gdb
[not found] ` <CAJOr74gc9zeHQGST3eufT9zYJEsdEkO4m4xgxhQyQNE3kpSUNw@mail.gmail.com>
2025-05-29 9:16 ` Eli Zaretskii via Gdb
2025-05-28 7:44 ` Mark Wielaard
2025-05-28 12:30 ` Guinevere Larsen via Gdb
2025-05-30 11:22 ` Florian Weimer via Gdb
2025-05-30 20:39 ` Mark Wielaard [this message]
2025-05-28 11:47 ` Eli Zaretskii via Gdb
2025-05-28 11:39 ` Eli Zaretskii via Gdb
2025-05-28 12:15 ` Guinevere Larsen via Gdb
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250530203901.GC15893@gnu.wildebeest.org \
--to=mark@klomp.org \
--cc=fweimer@redhat.com \
--cc=gdb@sourceware.org \
--cc=guinevere@redhat.com \
--cc=psmith@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox