Path: csiph.com!goblin1!goblin.stu.neva.ru!usenet.stanford.edu!not-for-mail
From: Bruce Lilly <bruce.lilly@gmail.com>
Newsgroups: gnu.bash.bug
Subject: Re: Bash parameter expansion (remove largest trailing match, remove largest leading match, pattern replacement) does not work
Date: Sat, 29 Aug 2020 15:54:12 -0400
Lines: 16
Approved: bug-bash@gnu.org
Message-ID: <mailman.1735.1598730873.2469.bug-bash@gnu.org>
References: <CAPyES363zNvUZHWo6imXOyC3UPU5FAbsyFGzWkcJMO-HBhT6gQ@mail.gmail.com> <CAFLRLk_k+J3-Nt9UJ4Fb8c-RewPnVjf_b=ShqGGASG0GmREAhg@mail.gmail.com> <CAPyES3685SjyZfrL+M_56wGqxvh=N9xNchWJ1xqMSrmmEJb9ww@mail.gmail.com> <CAMLQOtQtYxMiiP9=nN72AKC+hKTJ06rLxM7=Nt5LF1M47jvWrA@mail.gmail.com> <CAPyES36MM0OL2gDnaqfpywoyRwk29NWSXWTNFSCgA4a+jBfENQ@mail.gmail.com> <CAFLRLk8eb+PNzuGp_teBrEZC=U1oHMa66vFcch3pH=eEmt6+=Q@mail.gmail.com> <CAPyES34VNuisQZy-pa75yL2MPzrR8UoD_bwZp6B8eR7Ko=xG0g@mail.gmail.com>
NNTP-Posting-Host: lists.gnu.org
Mime-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Cc: bug-bash@gnu.org
To: Koichi Murase <myoga.murase@gmail.com>
Envelope-to: bug-bash@gnu.org
In-Reply-To: <CAFLRLk8eb+PNzuGp_teBrEZC=U1oHMa66vFcch3pH=eEmt6+=Q@mail.gmail.com>
Received-SPF: pass client-ip=2607:f8b0:4864:20::12f; envelope-from=bruce.lilly@gmail.com; helo=mail-il1-x12f.google.com
X-Spam_score_int: -20
X-Spam_score: -2.1
X-Spam_bar: --
X-Spam_report: (-2.1 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no
X-Spam_action: no action
X-Content-Filtered-By: Mailman/MimeDel 2.1.23
X-BeenThere: bug-bash@gnu.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Bug reports for the GNU Bourne Again SHell <bug-bash.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/bug-bash>, <mailto:bug-bash-request@gnu.org?subject=unsubscribe>
List-Archive: <https://lists.gnu.org/archive/html/bug-bash>
List-Post: <mailto:bug-bash@gnu.org>
List-Help: <mailto:bug-bash-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/bug-bash>, <mailto:bug-bash-request@gnu.org?subject=subscribe>
X-Mailman-Original-Message-ID: <CAPyES34VNuisQZy-pa75yL2MPzrR8UoD_bwZp6B8eR7Ko=xG0g@mail.gmail.com>
X-Mailman-Original-References: <CAPyES363zNvUZHWo6imXOyC3UPU5FAbsyFGzWkcJMO-HBhT6gQ@mail.gmail.com> <CAFLRLk_k+J3-Nt9UJ4Fb8c-RewPnVjf_b=ShqGGASG0GmREAhg@mail.gmail.com> <CAPyES3685SjyZfrL+M_56wGqxvh=N9xNchWJ1xqMSrmmEJb9ww@mail.gmail.com> <CAMLQOtQtYxMiiP9=nN72AKC+hKTJ06rLxM7=Nt5LF1M47jvWrA@mail.gmail.com> <CAPyES36MM0OL2gDnaqfpywoyRwk29NWSXWTNFSCgA4a+jBfENQ@mail.gmail.com> <CAFLRLk8eb+PNzuGp_teBrEZC=U1oHMa66vFcch3pH=eEmt6+=Q@mail.gmail.com>
Xref: csiph.com gnu.bash.bug:16855

On Sat, Aug 29, 2020, 15:40 Koichi Murase <myoga.murase@gmail.com> wrote:

> Don't worry.  In this case, the GPL doesn't apply.  Please read the
> following Q&A.
>
> https://www.gnu.org/licenses/gpl-faq.en.html#IfInterpreterIsGPL
>
> Even if your original `shellbug' is licensed under something other,
> and it prohibits to make it public, you can still create another
> script to reproduce the same issue.  [...]
>
It's a bit more complicated than that; if, for example, some excerpt ended
up in regression tests, there would be a question about whether or not
there was a copyright violation.  As I understand the GPL (IANAL), it
requires all parts of a "work" to be GPL'd, and that wouldn't be possible
for any parts of the script that ended up in bash regression tests.