From 7ad3f7b2f6c6e4719e5398153ddb3e320cf84f67 Mon Sep 17 00:00:00 2001 From: Ribbon Date: Fri, 6 Jun 2025 08:46:18 -0300 Subject: [PATCH] Remove the library linking policies --- README.md | 6 ------ 1 file changed, 6 deletions(-) diff --git a/README.md b/README.md index e777fdd7d..a20e95e21 100644 --- a/README.md +++ b/README.md @@ -17,7 +17,6 @@ from the [redox](https://gitlab.redox-os.org/redox-os/redox) repository. - [Search Recipes](#search-recipes) - [Package Policy](#package-policy) - [Cross-Compilation](#cross-compilation) - - [Library Linking](#library-linking) - [ABI stability](#abi-stability) - [Checksum](#checksum) - [License](#license) @@ -70,11 +69,6 @@ Before sending your recipe to upstream (to become a public package), you must fo - Don't use the auto-generated tarballs from GitHub, they aren't static and don't verify the archive integrity. -#### Library Linking - -- Keep the static linking of libraries to reduce the launch time and improve security. -- If your package is bigger than 50MB, dynamic link big libraries until your package is equal or less than 50MB (to reduce the RAM usage). - #### ABI stability - Respect the ABI separation of the libraries, for example, if `openssl1` is available and some program need `openssl3`, you will create a recipe for `openssl3` and not rename the `openssl1`, as it will break the dependent packages.