forked from openkylin/docs
!2 update en/Community-Developer-Guides/Software_Package_Copyright_Supplement_Guide.md.
Merge pull request !2 from wucaiheng/N/A
This commit is contained in:
Gitee
commit
cf8e1abb71
|
|
@ -6,10 +6,10 @@ tags:
|
|||
|
||||
# openKylin package copyright agreement supplementary guide
|
||||
|
||||
openKylin is very strict about package copyright and license information, all packages in openKylin should contain the corresponding copyright information, generally including the following three steps: 1.
|
||||
1. placing the appropriate copyright notice file in the header comments of each source file.
|
||||
openKylin is very strict about package copyright and license information. All packages in openKylin should contain the corresponding copyright information, generally including the following three steps: 1.
|
||||
1. place the appropriate copyright notice file in the header comments of each source file.
|
||||
2. create a file named "LICENSE" or "COPYING" in the package's first-level directory and put the license information for the entire project.
|
||||
3. provide a summary of the copyright information of all source files of the project in the debian/copyright file.
|
||||
3. provide a summary of the copyright information of all source files of the project in the Debian/copyright file.
|
||||
|
||||
**It is recommended that new open source projects use the [Mulan PSL v2 protocol](http://license.coscl.org.cn/index.html).** Mulan PSL v2 is similar to BSD-type licenses and has good compatibility: BSD and MIT-type loose licenses are compatible with the Mulan PSL v2 protocol. The Mulan PSL v2 protocol is compatible with Apache License v2.0, L/GPLv2, L/GPLv3, and other licenses. That is, code licensed under BSD, MIT class licenses can contribute to projects using the Mulan PSL v2 protocol; code using the Mulan PSL v2 protocol can contribute to projects such as Apache License v2.0, L/GPLv2 or L/GPLv3.
|
||||
|
||||
|
|
@ -61,7 +61,7 @@ cp /usr/share/common-license/GPL-3 COPYING
|
|||
## debian/copyright file
|
||||
### File syntax
|
||||
|
||||
The debian/copyright file must convey all required upstream information, copyright notices, and license details in a file consisting of two or more paragraphs. At a minimum, the file must include a title paragraph and a document paragraph.
|
||||
The Debian/copyright file must convey all required upstream information, copyright notices, and license details in a file consisting of two or more paragraphs. At a minimum, the file must include a title paragraph and a document paragraph.
|
||||
|
||||
### Paragraphs
|
||||
|
||||
|
|
@ -80,7 +80,6 @@ The following fields can appear in a header paragraph
|
|||
- License: Optional.
|
||||
- Copyright: Optional.
|
||||
|
||||
The Copyright and License in the title paragraph may supplement, but not replace, the Files paragraph. They can be used to summarize the contribution and redistribution terms of an entire package, for example, when a work combines permissive and free copy licenses, or to document the copyright and license of a compilation. It is possible to use only License in the title paragraph; using Copyright alone would be meaningless.
|
||||
|
||||
#### Files paragraph (repeatable)
|
||||
|
||||
|
|
@ -104,7 +103,7 @@ The following fields can appear in separate license paragraphs.
|
|||
|
||||
### Fields
|
||||
|
||||
The following fields are defined for use in debian/copyright.
|
||||
The following fields are defined for use in Debian/copyright.
|
||||
|
||||
#### Format
|
||||
|
||||
|
|
@ -112,7 +111,7 @@ Type: single line value.
|
|||
|
||||
The file format follows the canonical address, e.g.
|
||||
|
||||
- Format: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/.
|
||||
- Format: https://www.Debian.org/doc/packaging-manuals/copyright-format/1.0/.
|
||||
|
||||
#### Upstream-Name
|
||||
|
||||
|
|
@ -127,7 +126,6 @@ Type: row-based list;
|
|||
The preferred address to reach the upstream project. May be free-form text, but by convention it is usually written as a list of RFC5322 addresses or URIs.
|
||||
|
||||
#### Source
|
||||
|
||||
Type: formatted text, no summary.
|
||||
|
||||
An explanation of the upstream source. Normally this would be a URL, but it may be a free-form interpretation. If the upstream source has been modified to remove non-free parts, this should be specified in this field.
|
||||
|
|
@ -181,7 +179,7 @@ The copyright field can contain an exact copy of the original copyright notice (
|
|||
|
||||
Type: a space-separated list.
|
||||
|
||||
Indicates a list of patterns for the files covered by the licenses and copyrights specified in this paragraph.
|
||||
Indicates the schema list of documents covered by the licenses and copyrights specified in this paragraph.
|
||||
|
||||
The filename patterns in the file field are specified using the simplified shell glob syntax. Patterns are separated by spaces.
|
||||
|
||||
|
|
@ -223,7 +221,7 @@ A GPL-2+ work with an OpenSSL exception is actually a dual-licensed work that ca
|
|||
|
||||
License: GPL-2+ with OpenSSL exception
|
||||
|
||||
debian/copyright can be found in [example](https://gitee.com/openkylin/ukui-session-manager/blob/openkylin/yangtze/debian/copyright "example")
|
||||
Debian/copyright can be found in [example](https://gitee.com/openKylin/ukui-session-manager/blob/openKylin/yangtze/debian/copyright "example")
|
||||
|
||||
## How to check copyright
|
||||
|
||||
|
|
|
|||
Loading…
Reference in New Issue