Skip to content
Snippets Groups Projects
Commit 66b924fa authored by Jeremy Soller's avatar Jeremy Soller
Browse files

Merge branch 'update-readme-links' into 'master'

Update README doc links

See merge request !422
parents 819eb501 7aa8203a
No related branches found
No related tags found
1 merge request!422Update README doc links
...@@ -6,7 +6,7 @@ This repository contains the system source code and packages inside the `recipes ...@@ -6,7 +6,7 @@ This repository contains the system source code and packages inside the `recipes
- A recipe can be a software port or system package (they use `pkgar` or `tar.gz` formats). - A recipe can be a software port or system package (they use `pkgar` or `tar.gz` formats).
**Read [this](https://doc.redox-os.org/book/ch09-03-porting-applications.html) page before porting programs to Redox** **Read [this](https://doc.redox-os.org/book/porting-applications.html) page before porting programs to Redox**
In order for this repository to be useful, it must be set up with an environment In order for this repository to be useful, it must be set up with an environment
from the [redox](https://gitlab.redox-os.org/redox-os/redox) repository. from the [redox](https://gitlab.redox-os.org/redox-os/redox) repository.
...@@ -63,7 +63,7 @@ Before sending your recipe to upstream (to become a public package), you must fo ...@@ -63,7 +63,7 @@ Before sending your recipe to upstream (to become a public package), you must fo
#### Cross-Compilation #### Cross-Compilation
- All recipes must use our cross-compilers, a Cookbook [template](https://doc.redox-os.org/book/ch09-03-porting-applications.html#templates) does this automatically but it's not always possible, study the build system of your program or library to find these options or patch the configuration files. - All recipes must use our cross-compilers, a Cookbook [template](https://doc.redox-os.org/book/porting-applications.html#templates) does this automatically but it's not always possible, study the build system of your program or library to find these options or patch the configuration files.
- Don't hardcode the CPU architecture on the recipe script (this would break the multi-arch support). - Don't hardcode the CPU architecture on the recipe script (this would break the multi-arch support).
#### Tarballs #### Tarballs
...@@ -81,12 +81,12 @@ Before sending your recipe to upstream (to become a public package), you must fo ...@@ -81,12 +81,12 @@ Before sending your recipe to upstream (to become a public package), you must fo
#### Checksum #### Checksum
- If your recipe download a tarball, you will need to create a BLAKE3 hash for it. You can learn how to do it [here](https://doc.redox-os.org/book/ch09-03-porting-applications.html#create-a-blake3-hash-for-your-recipee). - If your recipe download a tarball, you will need to create a BLAKE3 hash for it. You can learn how to do it [here](https://doc.redox-os.org/book/porting-applications.html#create-a-blake3-hash-for-your-recipe).
#### License #### License
- Don't package programs or libraries lacking a license. - Don't package programs or libraries lacking a license.
- Verify if the program has some license violation, in case of doubt ask us on the [chat](https://doc.redox-os.org/book/ch13-01-chat.html). - Verify if the program has some license violation, in case of doubt ask us on the [chat](https://doc.redox-os.org/book/chat.html).
- Non-free programs and assets should go to a subcategory of the `nonfree` category and be approved per license. - Non-free programs and assets should go to a subcategory of the `nonfree` category and be approved per license.
### Testing Area ### Testing Area
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment