svn commit: r363091 - in head/contrib/bc: . include manuals src tests tests/bc

[Stefan Eßer]

Am 30.07.20 um 18:31 schrieb Baptiste Daroussin:
> On Thu, Jul 30, 2020 at 05:28:19PM +0100, Jessica Clarke wrote:
>> On 30 Jul 2020, at 17:20, Baptiste Daroussin <bapt at FreeBSD.org> wrote:
>>> On Sat, Jul 11, 2020 at 07:33:19AM +0000, Stefan Eßer wrote:
>>>> Author: se
>>>> Date: Sat Jul 11 07:33:18 2020
>>>> New Revision: 363091
>>>> URL: https://svnweb.freebsd.org/changeset/base/363091
>>>>
>>>> Log:
>>>>  Update to version 3.1.3
>>>>
>>> Jumping on that commit, since the switch from our previous bc.
>>>
>>> The output of the interactive bc has changed, the previous version had a clean
>>> UI, the new version "pollutes" the output with plenty of lines about the
>>> copyright:
>>>
>>> ====
>>> Copyright (c) 2018-2020 Gavin D. Howard and contributors
>>> Report bugs at: https://git.yzena.com/gavin/bc
>>>
>>> This is free software with ABSOLUTELY NO WARRANTY.
>>> ====
>>>
>>> Imagine if all programs where doing that, it would be painful, do you think
>>> upstream can be convinced to remove those lines?
>>>
>>> I no the GNU version also has the same polluted output which was one of the
>>> reason I was happy with out previous version of bc.
>>
>> By default both will print such a banner if and only if being called
>> interactively. You can disable the banner explicitly with -q/--quiet
>> for both GNU bc and this bc. I agree it's a bit noisy and would be
>> nicer to not have that printed, but it's not without precedent for
>> REPL-like things.
> 
> Yes it is not without precedent for REPL-like things, still I dislike this and
> would be happy to get bc interactive be as nice as the previous one we had :)
> 
> If not I will deal with it and just yell internally each time I run it :D

I'll forward this thread to the author - had already stated similar
thought to him for consideration.

Is very interested to prevent forks of his software - although not
forbidden by the license - but he wants to keep his sources as the
official and "clean" upstream for other projects.

My guess is that he'll add a compile time switch to his version
that will be added to our usr.bin Makefile and will suppress the
start-up message in our base system version. (I'll keep the port
version as is unless there is a strong preference to suppress it
also in the port).

I'd expect it to take a few days (since he only tags new versions
after running a fuzzer for a few days if non-trivial changes have
been performed and I know he improved something in the interpreter
without publishing it, yet) ...

Regards, STefan