I am far from an expert in this field myself so I don't know whether
including it in the text section of the binary would be enough, and the
main issue for me is when clients of mine redistribute middleware in
their turn as I mentioned in an earlier post. But either way, Richard
already cleared this up so there's no more ambiguity on my end.
Kind regards,
Philip
On 5/7/2018 11:11 PM, Warren Young wrote:
On May 7, 2018, at 9:53 AM, Philip Bennefall <[email protected]> wrote:
It was merely an idea to possibly avoid some potential ambiguity regarding
public domain, which is a bit of a gray area in many places.
So take the code under the explicit license, then.
In my non-expert opinion, the worry over attribution is bogus. Restriction 2
in the 2-clause BSD license just requires that the license text itself be in
the binary, not that you “attribute” the software in your documentation or in a
startup banner as is required by some other licenses.
Fossil itself doesn’t bother to do even that:
$ strings `which fossil` | grep 'IMPLIED WARRANTIES'
_______________________________________________
sqlite-users mailing list
[email protected]
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
_______________________________________________
sqlite-users mailing list
[email protected]
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
