From: Philippe Blain <levraiphilippeblain@gmail.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb@sourceware.org
Subject: Re: Add script to setup codesigning on macOS
Date: Fri, 13 Dec 2019 22:41:00 -0000 [thread overview]
Message-ID: <625FCCFB-9AF7-4A91-B2AD-3CEBF7784026@gmail.com> (raw)
In-Reply-To: <20191212230518.GC2511@adacore.com>
I don’t think that would be a problem for me.
The original script in LLDB does not have a specific license, so I guess the general LLDB license [1] (Apache 2.0) would apply to that file. From what I understand that would be OK for GDB but I don’t know a lot about these things.
I’ll get started !
Philippe.
[1] https://github.com/llvm-mirror/lldb/blob/master/LICENSE.TXT
Le 12 déc. 2019 à 18:05, Joel Brobecker <brobecker@adacore.com> a écrit :
>> I’m interested in setting up a macOS build of GDB on conda-forge ([1],
>> [2]) and it seems that in order to do it the codesigning procedure
>> would have to be automated, i.e. entirely command-line driven. The
>> LLDB project already has a script doing exactly that [3], and I was
>> thinking of adding such a script to the conda-forge GDB feedstock.
>> However, I thought it could be a good idea to add it directly to the
>> GDB repository. Would a patch adding such a script be well received ?
>
> Not speaking for the entire group, but from my perspective,
> I don't see an objection off-hand to the idea of having it in
> the GDB repository. However, the GDB projects only accepts
> contributions that are either small or obvious enough to be
> accepted as is. For other contributions such as this one (IMO)
> that do not qualify, you need to be able to assign the copyrigh
> of that file to the FSF (need copyright assignment on file, and
> have permission to assign the copyright to the FSF).
>
> --
> Joel
prev parent reply other threads:[~2019-12-13 22:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-12 2:36 Philippe Blain
2019-12-12 23:05 ` Joel Brobecker
2019-12-13 22:41 ` Philippe Blain [this message]
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=625FCCFB-9AF7-4A91-B2AD-3CEBF7784026@gmail.com \
--to=levraiphilippeblain@gmail.com \
--cc=brobecker@adacore.com \
--cc=gdb@sourceware.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