bonsai/repo
4
0
Fork 0
forked from kiss-community/repo
Code Issues 28 Pull Requests 2 Projects Releases Activity

docs: update

Browse Source
This commit is contained in:
Muhammad Herdiansyah 2019-07-04 21:25:06 +07:00
parent 58b39a394f
commit bef0fd636e
1 changed files with 0 additions and 24 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

24
README.md
View File

@ -10,7 +10,6 @@ Each Package is split into multiple files.
zlib/ # Package name.
├─ build # Build script.
├─ depends # Dependencies (one per line) (sometimes optional).
├─ licenses # Licenses (see below).
├─ sources # Sources (one per line).
├─ version # Package version.
┘
@ -53,7 +52,6 @@ This also means anyone can write a tool to manipulate the repository or even the
* [`depends`](#depends)
* [`version`](#version)
* [`checksums`](#checksums)
* [`licenses`](#licenses)
* [`post-install`](#post-install)
<!-- vim-markdown-toc -->
@ -153,28 +151,6 @@ The `checksums` file contains the `sha256` sums of each entry in the `sources` f
c3e5e9fdd5004dcb542feda5ee4f0ff0744628baf8ed2dd5d66f8ca1197cb1a1 zlib-1.2.11.tar.gz
```
### `licenses`
The `licenses` file contains the license(s) of the package. Licenses such as `GPL`, `AGPL`, `LGPL`, `MPL`, `Artistic`, `CDDL`, or `Apache` can be written with [SPDX Short Identifier](https://spdx.org/licenses/) one per line, but for license exceptions or copyright notice licenses such as `BSD`, `MIT`, or `ISC`, the copyright notice must be included verbatim.
```
GPL-3.0-or-later
The ISC License
Copyright <YEAR> <OWNER>
Permission to use, copy, modify, and/or distribute this software for
any purpose with or without fee is hereby granted, provided that the
above copyright notice and this permission notice appear in all copies.
THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES
WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR
ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES
WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN
ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF
OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
```
### `post-install`
The `post-install` file should contain any steps required directly after the package is installed. This includes updating font databases and creating any post-install symlinks which may be required.