From b5c9367cc401badd2391868cc45ea892e5ae7fc9 Mon Sep 17 00:00:00 2001 From: iphydf Date: Sun, 31 Dec 2023 17:22:58 +0000 Subject: [PATCH] chore: Use GPL license with https. This aligns with the new zig-toxcore-c repo. It is a chore, but better than changing the zig-toxcore-c license to not use https. --- BUILD.bazel | 2 +- LICENSE | 9 ++++----- 2 files changed, 5 insertions(+), 6 deletions(-) diff --git a/BUILD.bazel b/BUILD.bazel index 64d91f5..a3ee0ee 100644 --- a/BUILD.bazel +++ b/BUILD.bazel @@ -1,3 +1,3 @@ load("//tools/project:build_defs.bzl", "project") -project() +project(license = "gpl3-https") diff --git a/LICENSE b/LICENSE index 10926e8..f288702 100644 --- a/LICENSE +++ b/LICENSE @@ -1,7 +1,7 @@ GNU GENERAL PUBLIC LICENSE Version 3, 29 June 2007 - Copyright (C) 2007 Free Software Foundation, Inc. + Copyright (C) 2007 Free Software Foundation, Inc. Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. @@ -645,7 +645,7 @@ the "copyright" line and a pointer to where the full notice is found. GNU General Public License for more details. You should have received a copy of the GNU General Public License - along with this program. If not, see . + along with this program. If not, see . Also add information on how to contact you by electronic and paper mail. @@ -664,12 +664,11 @@ might be different; for a GUI interface, you would use an "about box". You should also get your employer (if you work as a programmer) or school, if any, to sign a "copyright disclaimer" for the program, if necessary. For more information on this, and how to apply and follow the GNU GPL, see -. +. The GNU General Public License does not permit incorporating your program into proprietary programs. If your program is a subroutine library, you may consider it more useful to permit linking proprietary applications with the library. If this is what you want to do, use the GNU Lesser General Public License instead of this License. But first, please read -. - +.