From: Eli Zaretskii <eliz@gnu.org>
To: Andrew Burgess <andrew.burgess@embecosm.com>
Cc: gdb-patches@sourceware.org, richard.bunt@arm.com
Subject: Re: [PATCH] gdb: Allow more control over where to find python libraries
Date: Wed, 19 Feb 2020 15:57:00 -0000 [thread overview]
Message-ID: <83blpulgdx.fsf@gnu.org> (raw)
In-Reply-To: <20200219155350.GC3317@embecosm.com> (message from Andrew Burgess on Wed, 19 Feb 2020 15:53:50 +0000)
> Date: Wed, 19 Feb 2020 15:53:50 +0000
> From: Andrew Burgess <andrew.burgess@embecosm.com>
> Cc: gdb-patches@sourceware.org, richard.bunt@arm.com
>
> The use for this would be that at XXX organisation I can build a
> version of GDB, package it up into a tar-file and copy this onto
> several different machines, which might be running different OS
> versions.
>
> In this situation I don't think there's any licensing issue as the
> builds of GDB are not going outside the XXX organisation.
>
> If I did decide to distribute the pre-built GDB tar-files outside of
> XXX, then the source for GDB, and the source for Python would be made
> available also from XXX, but I didn't believe simply distributing two
> pre-built things in one package means I have to upstream merge the two
> projects - have I miss-understood?
If this is for private use between you and yourself, more or less,
then there's no problem, indeed.
next prev parent reply other threads:[~2020-02-19 15:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-06 16:46 Andrew Burgess
2020-02-06 18:31 ` Eli Zaretskii
2020-02-19 15:53 ` Andrew Burgess
2020-02-19 15:57 ` Eli Zaretskii [this message]
2020-02-07 17:58 ` Simon Marchi
2020-02-08 0:22 ` Andrew Burgess
2020-02-19 16:27 ` [PATCHv2] " Andrew Burgess
2020-02-19 17:09 ` Eli Zaretskii
2020-02-20 17:00 ` Tom Tromey
2020-02-20 19:22 ` Andrew Burgess
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=83blpulgdx.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=andrew.burgess@embecosm.com \
--cc=gdb-patches@sourceware.org \
--cc=richard.bunt@arm.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