public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: lkcl <luke.leighton@gmail.com>
To: Nick Alcock <nick.alcock@oracle.com>
Cc: lkcl via Binutils <binutils@sourceware.org>,
	Dmitry Selyutin <ghostmansd@gmail.com>
Subject: Re: Are big tests allowed in binutils?
Date: Tue, 21 Jun 2022 18:26:33 +0100	[thread overview]
Message-ID: <CAPweEDwkPPLs8boKu=FmP=FuGasBfRDU17ZiPYYUjg971J+MKw@mail.gmail.com> (raw)
In-Reply-To: <87sfnyxhbq.fsf@esperi.org.uk>

On Tue, Jun 21, 2022 at 2:43 PM Nick Alcock <nick.alcock@oracle.com> wrote:

> preferred form for modification in this case is pretty clearly not the
> generated testcases but the autogenerators themselves (and any input to
> them), so the GPL requires you to provide the generators too. They don't
> have to be in the binutils repo, but honestly putting them in there so
> people can manually run them if needed seems like a good idea. (Stick
> in simple pointers to the deps as well, particularly if just figuring ou
> what the deps *are* would otherwise be difficult, as "absolutely mental"
> suggests it would be).

*click*. of course.  you don't commit the source code of llvm to
the binutils repo just because it's a tool that's required, even
though the GPL states clearly that the tool(s) must be *available*.

(i mention llvm deliberately because, like the tools we use to
auto-generate the tests, it's also not GPL-licensed).

describing where those tools are is a good call.

l.

  reply	other threads:[~2022-06-21 17:26 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-17  5:11 Dmitry Selyutin
2022-06-17  6:19 ` Dmitry Selyutin
2022-06-20 10:42   ` Nick Alcock
2022-06-20 11:31     ` lkcl
2022-06-21 13:43       ` Nick Alcock
2022-06-21 17:26         ` lkcl [this message]
2022-06-21 17:29           ` Dmitry Selyutin
2022-06-21 19:23             ` lkcl
2022-06-17  9:14 ` Andreas Schwab
2022-06-21 15:32 ` Richard Earnshaw
2022-06-21 16:28   ` Dmitry Selyutin
2022-06-22  6:55     ` Jan Beulich

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='CAPweEDwkPPLs8boKu=FmP=FuGasBfRDU17ZiPYYUjg971J+MKw@mail.gmail.com' \
    --to=luke.leighton@gmail.com \
    --cc=binutils@sourceware.org \
    --cc=ghostmansd@gmail.com \
    --cc=nick.alcock@oracle.com \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).